Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f0000e79cf216f4c15c44f08520ce1a4f9cb8aa5362f93d7d3ab69fd75e693

Tx prefix hash: 137d027f05bdcdd0a2ac89e15fee0e79777b1493d60b74ab6ca042800b7784b3
Tx public key: be5e4bd4a702802f92ccce136fb535b05b1991d472dc0c63e03190ab3038d332
Timestamp: 1714284871 Timestamp [UCT]: 2024-04-28 06:14:31 Age [y:d:h:m:s]: 00:305:10:04:56
Block: 1010165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218315 RingCT/type: yes/0
Extra: 01be5e4bd4a702802f92ccce136fb535b05b1991d472dc0c63e03190ab3038d33202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf52e89e3ccad4b57da490a5690fc9f9f3e2f5d483bbefb97fecf41b05a953a8 0.600000000000 1472041 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": 1010175, "vin": [ { "gen": { "height": 1010165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf52e89e3ccad4b57da490a5690fc9f9f3e2f5d483bbefb97fecf41b05a953a8" } } ], "extra": [ 1, 190, 94, 75, 212, 167, 2, 128, 47, 146, 204, 206, 19, 111, 181, 53, 176, 91, 25, 145, 212, 114, 220, 12, 99, 224, 49, 144, 171, 48, 56, 211, 50, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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