Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e109d115a7bae2361486fc2d095dea3dd6d769df2e603801a83462112b5980

Tx prefix hash: 84d8ce7336cbf75f1cfa08943c7bf60fc4efc3c6720520759ddc7cbd0c4b07aa
Tx public key: 37981d6b75d1d1293c5abdc011d136c03f0933cb99fe1b6f2513e838b9593faf
Timestamp: 1731900683 Timestamp [UCT]: 2024-11-18 03:31:23 Age [y:d:h:m:s]: 00:213:10:01:42
Block: 1156121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152274 RingCT/type: yes/0
Extra: 0137981d6b75d1d1293c5abdc011d136c03f0933cb99fe1b6f2513e838b9593faf021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c2139f17462ed7934e7f26d7f28ce46d07ce1427ee3797e4ec35202f8702d1 0.600000000000 1641744 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": 1156131, "vin": [ { "gen": { "height": 1156121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c2139f17462ed7934e7f26d7f28ce46d07ce1427ee3797e4ec35202f8702d1" } } ], "extra": [ 1, 55, 152, 29, 107, 117, 209, 209, 41, 60, 90, 189, 192, 17, 209, 54, 192, 63, 9, 51, 203, 153, 254, 27, 111, 37, 19, 232, 56, 185, 89, 63, 175, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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