Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbebcffb9d2130a849b90436a9fcd30355b6d27b2eb107df14c57d33f80e11a4

Tx prefix hash: 884a6a17aa2028697c81ae63c5472a9a81bce76555b538d993816c7018306a55
Tx public key: 998007b0a6277d9f4290a128cea316d74b5954efb32f9b3d3dcad1069e93a1dc
Timestamp: 1726435907 Timestamp [UCT]: 2024-09-15 21:31:47 Age [y:d:h:m:s]: 00:209:21:13:47
Block: 1110911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149840 RingCT/type: yes/0
Extra: 01998007b0a6277d9f4290a128cea316d74b5954efb32f9b3d3dcad1069e93a1dc02110000000591e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 66ce6578b427fbd546cc7e210acd822ad64d40cbdce57d6fe7f7768128923d69 0.608000000000 1589684 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": 1110921, "vin": [ { "gen": { "height": 1110911 } } ], "vout": [ { "amount": 608000000, "target": { "key": "66ce6578b427fbd546cc7e210acd822ad64d40cbdce57d6fe7f7768128923d69" } } ], "extra": [ 1, 153, 128, 7, 176, 166, 39, 125, 159, 66, 144, 161, 40, 206, 163, 22, 215, 75, 89, 84, 239, 179, 47, 155, 61, 61, 202, 209, 6, 158, 147, 161, 220, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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