Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 198d0c39176e3013d576e21e92011b6bd7f87f13c2c40de09937f6e111a7e1ab

Tx prefix hash: 890de683cfe64418e2f3b62c698cf7d8b4c9bacc4701d5c547db254e112860ab
Tx public key: fd8b154292603cb5e8b73f45dde7c019b225633237d5d197563df5181448c61f
Timestamp: 1723350674 Timestamp [UCT]: 2024-08-11 04:31:14 Age [y:d:h:m:s]: 00:310:03:11:27
Block: 1085332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221472 RingCT/type: yes/0
Extra: 01fd8b154292603cb5e8b73f45dde7c019b225633237d5d197563df5181448c61f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1702dbb54d278260fb793cbb4bed7d4cbcb39e0eef071fc2ebb348b11ffe34a3 0.600000000000 1559893 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": 1085342, "vin": [ { "gen": { "height": 1085332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1702dbb54d278260fb793cbb4bed7d4cbcb39e0eef071fc2ebb348b11ffe34a3" } } ], "extra": [ 1, 253, 139, 21, 66, 146, 96, 60, 181, 232, 183, 63, 69, 221, 231, 192, 25, 178, 37, 99, 50, 55, 213, 209, 151, 86, 61, 245, 24, 20, 72, 198, 31, 2, 17, 0, 0, 0, 5, 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