Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f37a9c1353699e70b25f516c1e810aec11d09222d92f6aa70181c15d6739d86

Tx prefix hash: 147ec4a3f8138eb1a5187a995e82e70eaf37827579fb548e010122063252a58d
Tx public key: e015ccabbd28d6cf933b2be3f876c6e4e4ab114866b61338a3f5e571227baf14
Timestamp: 1714532395 Timestamp [UCT]: 2024-05-01 02:59:55 Age [y:d:h:m:s]: 00:302:20:07:05
Block: 1012230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216448 RingCT/type: yes/0
Extra: 01e015ccabbd28d6cf933b2be3f876c6e4e4ab114866b61338a3f5e571227baf140211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b419e56578978be2a3485349d11a622a42bb27d2e3b1a296930bf5bfcf3e1de9 0.600000000000 1474692 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": 1012240, "vin": [ { "gen": { "height": 1012230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b419e56578978be2a3485349d11a622a42bb27d2e3b1a296930bf5bfcf3e1de9" } } ], "extra": [ 1, 224, 21, 204, 171, 189, 40, 214, 207, 147, 59, 43, 227, 248, 118, 198, 228, 228, 171, 17, 72, 102, 182, 19, 56, 163, 245, 229, 113, 34, 123, 175, 20, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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