Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457c859f40c767b602588f2a41f642380e18f7ca5994c2ee4919c74658e12dbd

Tx prefix hash: e9b3de33a6e8e871313a1103c55f9be153d0f13ec821c753d9c80d49df917d84
Tx public key: 29a4c6bc92a44903a6a36a90935cd9fd454345dbf1065fae34fb28310a0182c8
Timestamp: 1719931015 Timestamp [UCT]: 2024-07-02 14:36:55 Age [y:d:h:m:s]: 00:280:16:18:21
Block: 1056983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200549 RingCT/type: yes/0
Extra: 0129a4c6bc92a44903a6a36a90935cd9fd454345dbf1065fae34fb28310a0182c802110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34caac1eed13745fd9c411d867db70dc5b21aab2786dd1d77c412167f660e5a 0.600000000000 1527412 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": 1056993, "vin": [ { "gen": { "height": 1056983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34caac1eed13745fd9c411d867db70dc5b21aab2786dd1d77c412167f660e5a" } } ], "extra": [ 1, 41, 164, 198, 188, 146, 164, 73, 3, 166, 163, 106, 144, 147, 92, 217, 253, 69, 67, 69, 219, 241, 6, 95, 174, 52, 251, 40, 49, 10, 1, 130, 200, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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