Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74fccf9615e79390aecc25070f21764e72a34f149f8cfbadaa3325c38ebbc90a

Tx prefix hash: 3edb3d2100efd17d1ecc950717105e789faf5e13d75d65b2d20a3d8d6b7bafb5
Tx public key: 8668f6678d237f01d9e5de5dbfdb736e9f8e89a86eb3102712da112d40757135
Timestamp: 1699864413 Timestamp [UCT]: 2023-11-13 08:33:33 Age [y:d:h:m:s]: 01:155:13:46:38
Block: 890623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372376 RingCT/type: yes/0
Extra: 018668f6678d237f01d9e5de5dbfdb736e9f8e89a86eb3102712da112d4075713502110000000533af99f4000000000000000000

1 output(s) for total of 0.687062559000 dcy

stealth address amount amount idx
00: a7bfccbe24f9f5b595f468d929368e388b10b02e7c5c501af92a6e2bdf902b29 0.687062559000 1346648 of 0

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": 890633, "vin": [ { "gen": { "height": 890623 } } ], "vout": [ { "amount": 687062559, "target": { "key": "a7bfccbe24f9f5b595f468d929368e388b10b02e7c5c501af92a6e2bdf902b29" } } ], "extra": [ 1, 134, 104, 246, 103, 141, 35, 127, 1, 217, 229, 222, 93, 191, 219, 115, 110, 159, 142, 137, 168, 110, 179, 16, 39, 18, 218, 17, 45, 64, 117, 113, 53, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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