Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb22a25aabb91ea645fe3b6053124d55e6bb63658563b3abb3a65658c2f70a2

Tx prefix hash: 89418cf3e43d87d7f74ee86369de6bb7912faf98e1fe58b13001e81c684f1162
Tx public key: cd7d8aa1b17e7fe8ed3c4b02220e09e37b82352a0174cc75c0555cc0a2a0d457
Timestamp: 1727916721 Timestamp [UCT]: 2024-10-03 00:52:01 Age [y:d:h:m:s]: 00:185:05:05:20
Block: 1123194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132169 RingCT/type: yes/0
Extra: 01cd7d8aa1b17e7fe8ed3c4b02220e09e37b82352a0174cc75c0555cc0a2a0d45702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d479588040f561d7541fbf710a1ed8b25a0f31e75bb05558cad81797ed1842 0.600000000000 1605727 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": 1123204, "vin": [ { "gen": { "height": 1123194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d479588040f561d7541fbf710a1ed8b25a0f31e75bb05558cad81797ed1842" } } ], "extra": [ 1, 205, 125, 138, 161, 177, 126, 127, 232, 237, 60, 75, 2, 34, 14, 9, 227, 123, 130, 53, 42, 1, 116, 204, 117, 192, 85, 92, 192, 162, 160, 212, 87, 2, 17, 0, 0, 0, 3, 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