Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ff6c048547ff0033865f8fdd3281d75dd7ba3088020a244ca55aaefc05e293c0

Tx prefix hash: c0b690ba83a94149352c9d022dec6d99f7a5bcf685031e2420c663357bc9ec10
Tx public key: f0af251654d7d60154509fd31d436c3e445b8749fd8afc71d5c8455972a8acaf
Timestamp: 1712911142 Timestamp [UCT]: 2024-04-12 08:39:02 Age [y:d:h:m:s]: 01:006:00:51:35
Block: 998766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265288 RingCT/type: yes/0
Extra: 01f0af251654d7d60154509fd31d436c3e445b8749fd8afc71d5c8455972a8acaf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed96e40bf3e5897f494d43aa86f7eda273f12c2e4e07976f6e779f608e4ce821 0.600000000000 1459220 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 998776, "vin": [ { "gen": { "height": 998766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed96e40bf3e5897f494d43aa86f7eda273f12c2e4e07976f6e779f608e4ce821" } } ], "extra": [ 1, 240, 175, 37, 22, 84, 215, 214, 1, 84, 80, 159, 211, 29, 67, 108, 62, 68, 91, 135, 73, 253, 138, 252, 113, 213, 200, 69, 89, 114, 168, 172, 175, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8