Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451b6edd68d4f35dd37d113d005654ff16b7db804a7e4366864b97c35ab84eae

Tx prefix hash: f80d4bd6c1ab9fb173aa576b31cda1825cf30f4742d1fd7fbb411efdb6044fa1
Tx public key: 32c99517b0f5e53e16173098861d368a3a817444a38decaab3a53200a2f0916b
Timestamp: 1721587702 Timestamp [UCT]: 2024-07-21 18:48:22 Age [y:d:h:m:s]: 01:105:09:50:22
Block: 1070702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333852 RingCT/type: yes/0
Extra: 0132c99517b0f5e53e16173098861d368a3a817444a38decaab3a53200a2f0916b02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eee47c12911931fcbbc95df2da1a6d2591d933707e9e376f00b6ea319626aa5 0.600000000000 1542647 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": 1070712, "vin": [ { "gen": { "height": 1070702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eee47c12911931fcbbc95df2da1a6d2591d933707e9e376f00b6ea319626aa5" } } ], "extra": [ 1, 50, 201, 149, 23, 176, 245, 229, 62, 22, 23, 48, 152, 134, 29, 54, 138, 58, 129, 116, 68, 163, 141, 236, 170, 179, 165, 50, 0, 162, 240, 145, 107, 2, 17, 0, 0, 0, 6, 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