Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61486cce0c616a87a5f67a4b5c6fea384c312b6291776d1c5e147e1be1a31159

Tx prefix hash: cc5cae996eb63b62d98c6d60ae18047238fec164e44d2a63ba6bb021b51cc164
Tx public key: ebcd4560f147a624d20228b2a0e898bd97226e319c021484395cb5bf2b9ce2a9
Timestamp: 1737095777 Timestamp [UCT]: 2025-01-17 06:36:17 Age [y:d:h:m:s]: 00:154:12:53:04
Block: 1199137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110106 RingCT/type: yes/0
Extra: 01ebcd4560f147a624d20228b2a0e898bd97226e319c021484395cb5bf2b9ce2a9021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac5ccfe29d607511f7b5e61d9036d559749f29a7c5ac80aa053008ac5ac5ccf 0.600000000000 1685766 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": 1199147, "vin": [ { "gen": { "height": 1199137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac5ccfe29d607511f7b5e61d9036d559749f29a7c5ac80aa053008ac5ac5ccf" } } ], "extra": [ 1, 235, 205, 69, 96, 241, 71, 166, 36, 210, 2, 40, 178, 160, 232, 152, 189, 151, 34, 110, 49, 156, 2, 20, 132, 57, 92, 181, 191, 43, 156, 226, 169, 2, 17, 0, 0, 0, 9, 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