Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40244f053ab1b44518a79ba072a8474da6846f55164edaeb099db18dc4871929

Tx prefix hash: 486d925d31248b4fbc8d8a61f92533f5dc4d562ebbf8c39bd5b385c41e948a88
Tx public key: 76fbc755cc7f746a41a2ac0898ad44c19c4a2a59c8e4402d3eb76941ba0f4822
Timestamp: 1739106213 Timestamp [UCT]: 2025-02-09 13:03:33 Age [y:d:h:m:s]: 00:332:01:55:20
Block: 1215523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235168 RingCT/type: yes/0
Extra: 0176fbc755cc7f746a41a2ac0898ad44c19c4a2a59c8e4402d3eb76941ba0f4822021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e9f6a0d910331fa08c3bbb2b13706f8e3cdcac14e7f066e134bb06dbfde2d91 0.600000000000 1702322 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": 1215533, "vin": [ { "gen": { "height": 1215523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e9f6a0d910331fa08c3bbb2b13706f8e3cdcac14e7f066e134bb06dbfde2d91" } } ], "extra": [ 1, 118, 251, 199, 85, 204, 127, 116, 106, 65, 162, 172, 8, 152, 173, 68, 193, 156, 74, 42, 89, 200, 228, 64, 45, 62, 183, 105, 65, 186, 15, 72, 34, 2, 17, 0, 0, 0, 8, 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