Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258e52bc963c74e273ad3ec916ceb325ebad8229389fcea2ff8c2055572164e2

Tx prefix hash: 5da9bb152f84f3f1c570ede2794ff1174a06a4522fed7b559180b3f135c04b16
Tx public key: 018c09c344f79b96e9ff1e9c06e7734328542596d74573ea0b251f77f9dcc3c5
Timestamp: 1731521621 Timestamp [UCT]: 2024-11-13 18:13:41 Age [y:d:h:m:s]: 01:038:00:15:22
Block: 1152985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285629 RingCT/type: yes/0
Extra: 01018c09c344f79b96e9ff1e9c06e7734328542596d74573ea0b251f77f9dcc3c5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e939d9a252ef1769cf12d0ccb9dc915bdbec69799c0ac87b4c119153c9ea78 0.600000000000 1638592 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": 1152995, "vin": [ { "gen": { "height": 1152985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e939d9a252ef1769cf12d0ccb9dc915bdbec69799c0ac87b4c119153c9ea78" } } ], "extra": [ 1, 1, 140, 9, 195, 68, 247, 155, 150, 233, 255, 30, 156, 6, 231, 115, 67, 40, 84, 37, 150, 215, 69, 115, 234, 11, 37, 31, 119, 249, 220, 195, 197, 2, 17, 0, 0, 0, 3, 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