Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a32332c468d89bbf8e690d651b3fac8fec4fd7d910bfd4ba86917e9530a9edf

Tx prefix hash: 2ea7e1d2b3cf821d432269ca7d808127040dc9e0009f265d32f5d50dd4a8d44a
Tx public key: 25c0ca57488e4f2f9973779b44dc0f9e4b102c80aa4b0b2bc3e87c4692acdaf9
Timestamp: 1735341845 Timestamp [UCT]: 2024-12-27 23:24:05 Age [y:d:h:m:s]: 00:082:15:01:55
Block: 1184613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58872 RingCT/type: yes/0
Extra: 0125c0ca57488e4f2f9973779b44dc0f9e4b102c80aa4b0b2bc3e87c4692acdaf9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97896c7acc0ac4c5241cf780332d50a011ec60b5a558b0227eea4d4d41ce1307 0.600000000000 1671072 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": 1184623, "vin": [ { "gen": { "height": 1184613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97896c7acc0ac4c5241cf780332d50a011ec60b5a558b0227eea4d4d41ce1307" } } ], "extra": [ 1, 37, 192, 202, 87, 72, 142, 79, 47, 153, 115, 119, 155, 68, 220, 15, 158, 75, 16, 44, 128, 170, 75, 11, 43, 195, 232, 124, 70, 146, 172, 218, 249, 2, 17, 0, 0, 0, 5, 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