Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721c7e60f2f8d0fa99792262390aba5e03877f25779d0cd56577d4ecbffa3c82

Tx prefix hash: f7ec42fcc2ec78ee05a7b61bba45f60e0a40cad8932baddc994fd604563f099b
Tx public key: 244b7b3df3bc871963791c3bd4734d95bfe121a2e08c9dcd141786694b382a5c
Timestamp: 1705359306 Timestamp [UCT]: 2024-01-15 22:55:06 Age [y:d:h:m:s]: 01:340:19:33:57
Block: 936159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502456 RingCT/type: yes/0
Extra: 01244b7b3df3bc871963791c3bd4734d95bfe121a2e08c9dcd141786694b382a5c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 445b4981c20ea65934b03541677a1d2520974dd3ca76eedeaff4e6a7412ed128 0.600000000000 1394183 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": 936169, "vin": [ { "gen": { "height": 936159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "445b4981c20ea65934b03541677a1d2520974dd3ca76eedeaff4e6a7412ed128" } } ], "extra": [ 1, 36, 75, 123, 61, 243, 188, 135, 25, 99, 121, 28, 59, 212, 115, 77, 149, 191, 225, 33, 162, 224, 140, 157, 205, 20, 23, 134, 105, 75, 56, 42, 92, 2, 17, 0, 0, 0, 2, 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