Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ba82cca2c65ae4b29b5e5698039bac8215832ec3664b860ffb94fa3c6f3442

Tx prefix hash: 28536cfb6859b3990a36f16b0f5b003ab5f45c4d77db96e71fe9d60efdba94c2
Tx public key: c9c04185f881870ff17d0ec615bc4d43cc77e8e450f4a4f56b43c0526cae2bd1
Timestamp: 1734133986 Timestamp [UCT]: 2024-12-13 23:53:06 Age [y:d:h:m:s]: 00:113:17:25:02
Block: 1174639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81047 RingCT/type: yes/0
Extra: 01c9c04185f881870ff17d0ec615bc4d43cc77e8e450f4a4f56b43c0526cae2bd10211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0871e0ac620b417c0c7151478c7a2539429daca7e5dca953e7d6bc8aaf554ac9 0.600000000000 1660818 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": 1174649, "vin": [ { "gen": { "height": 1174639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0871e0ac620b417c0c7151478c7a2539429daca7e5dca953e7d6bc8aaf554ac9" } } ], "extra": [ 1, 201, 192, 65, 133, 248, 129, 135, 15, 241, 125, 14, 198, 21, 188, 77, 67, 204, 119, 232, 228, 80, 244, 164, 245, 107, 67, 192, 82, 108, 174, 43, 209, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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