Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3811b53536eae9808e7355ac9b2c653faa60e1b43d69c164ae9946454b64695

Tx prefix hash: 0ea966e38c0df500f680fa0b0f741c160f257040953102f7c51ae3efe79c1f72
Tx public key: 2c4c361cb406e80204fec1ca3ecc270579a8d5c3983a0172ae1e287ff758fd62
Timestamp: 1733316169 Timestamp [UCT]: 2024-12-04 12:42:49 Age [y:d:h:m:s]: 00:195:21:43:44
Block: 1167842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139746 RingCT/type: yes/0
Extra: 012c4c361cb406e80204fec1ca3ecc270579a8d5c3983a0172ae1e287ff758fd620211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b00cb515454e133047e866f66095de5ec038336d2ca6d8c8f358407b3cb21ad9 0.600000000000 1653545 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": 1167852, "vin": [ { "gen": { "height": 1167842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b00cb515454e133047e866f66095de5ec038336d2ca6d8c8f358407b3cb21ad9" } } ], "extra": [ 1, 44, 76, 54, 28, 180, 6, 232, 2, 4, 254, 193, 202, 62, 204, 39, 5, 121, 168, 213, 195, 152, 58, 1, 114, 174, 30, 40, 127, 247, 88, 253, 98, 2, 17, 0, 0, 0, 2, 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