Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f3e65170a61b22c1ce9cbebff6a173a52c6cdb70468cf1c094ca30bb03b898

Tx prefix hash: 6d2c4f7530d8565902d60987cb83566f8c46605e4b6adb5f0d3ce9d2ebbfaab8
Tx public key: 354bdc8c2e8f35e4eec33b39682d51dbc204208bd3453348ef11a0fbe83a4005
Timestamp: 1712760357 Timestamp [UCT]: 2024-04-10 14:45:57 Age [y:d:h:m:s]: 01:206:09:03:05
Block: 997508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406176 RingCT/type: yes/0
Extra: 01354bdc8c2e8f35e4eec33b39682d51dbc204208bd3453348ef11a0fbe83a40050211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef77d8dccfedeccc0eaf9779d729f2cfdc82437a274cf37f526ea9700f8f56c 0.600000000000 1457940 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": 997518, "vin": [ { "gen": { "height": 997508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef77d8dccfedeccc0eaf9779d729f2cfdc82437a274cf37f526ea9700f8f56c" } } ], "extra": [ 1, 53, 75, 220, 140, 46, 143, 53, 228, 238, 195, 59, 57, 104, 45, 81, 219, 194, 4, 32, 139, 211, 69, 51, 72, 239, 17, 160, 251, 232, 58, 64, 5, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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