Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e3d61580b548dbfdec8c0be112769f81aafec818a3af06da086b9b426141d70

Tx prefix hash: d10429507abad3b4c1748132108fc64005eaa30827e6cdab3451e4d03c6ee2c1
Tx public key: 73bf2d567371cf5c20985a8415efd5fa0e69ffc8a289f892fdb8cf4023102d7f
Timestamp: 1735363627 Timestamp [UCT]: 2024-12-28 05:27:07 Age [y:d:h:m:s]: 01:009:17:00:50
Block: 1184789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265403 RingCT/type: yes/0
Extra: 0173bf2d567371cf5c20985a8415efd5fa0e69ffc8a289f892fdb8cf4023102d7f021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fb5ce6d1370b766d92f29c27e2021f4c9f4222d5fb0aa0cb86f54ba427f92b 0.600000000000 1671248 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": 1184799, "vin": [ { "gen": { "height": 1184789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fb5ce6d1370b766d92f29c27e2021f4c9f4222d5fb0aa0cb86f54ba427f92b" } } ], "extra": [ 1, 115, 191, 45, 86, 115, 113, 207, 92, 32, 152, 90, 132, 21, 239, 213, 250, 14, 105, 255, 200, 162, 137, 248, 146, 253, 184, 207, 64, 35, 16, 45, 127, 2, 17, 0, 0, 0, 6, 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