Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a7d8d7f982ae5d65d30ef0bed585b8114d8b47efa14cc0455e1ed2fa60b9026

Tx prefix hash: 293412f28a170e9cd4852d06469a5c1614845ea98a8d9a3de2841c773d354451
Tx public key: 54e2ed90f876fbf05843dbba6953e87ad891a7fb944a40471f379dc4d82301f7
Timestamp: 1725394228 Timestamp [UCT]: 2024-09-03 20:10:28 Age [y:d:h:m:s]: 00:213:10:59:17
Block: 1102276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152407 RingCT/type: yes/0
Extra: 0154e2ed90f876fbf05843dbba6953e87ad891a7fb944a40471f379dc4d82301f702110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f0f78f05b393bc8d4c5a6229949435e6316aa375622433dc267f610ca0d9e4 0.600000000000 1578651 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": 1102286, "vin": [ { "gen": { "height": 1102276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f0f78f05b393bc8d4c5a6229949435e6316aa375622433dc267f610ca0d9e4" } } ], "extra": [ 1, 84, 226, 237, 144, 248, 118, 251, 240, 88, 67, 219, 186, 105, 83, 232, 122, 216, 145, 167, 251, 148, 74, 64, 71, 31, 55, 157, 196, 216, 35, 1, 247, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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