Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998cc221721f15d81a24d9e32fb7b62266124ffde6d77c046b27212a0e687646

Tx prefix hash: 593ed38ddef5e164966388b34464af2393099f268459d832d703f4411e7645cc
Tx public key: d76dfef4fe1f62b60036d98eb1e85307a83b0b49b786a937532a46375b8b3ded
Timestamp: 1734038763 Timestamp [UCT]: 2024-12-12 21:26:03 Age [y:d:h:m:s]: 00:337:03:20:39
Block: 1173853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238459 RingCT/type: yes/0
Extra: 01d76dfef4fe1f62b60036d98eb1e85307a83b0b49b786a937532a46375b8b3ded021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cc9a5d273f6a5a2d05e6b9cad3b5e41f3cab747dbe49463bd07444e9ca7d56d 0.600000000000 1659930 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": 1173863, "vin": [ { "gen": { "height": 1173853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cc9a5d273f6a5a2d05e6b9cad3b5e41f3cab747dbe49463bd07444e9ca7d56d" } } ], "extra": [ 1, 215, 109, 254, 244, 254, 31, 98, 182, 0, 54, 217, 142, 177, 232, 83, 7, 168, 59, 11, 73, 183, 134, 169, 55, 83, 42, 70, 55, 91, 139, 61, 237, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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