Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c332456db4f2d98619858f80e1bdeb25ca48284891ff2535a8a4ec6c5ec0e8b1

Tx prefix hash: 7526cae5f7eeaee9daba54506142a9efcb1a1cfec708067eead009e46743c751
Tx public key: e0b75f1616b64f8d4d33810e3e9a9a1313a8e7185afd90659aa2bdf9e0213e45
Timestamp: 1636654607 Timestamp [UCT]: 2021-11-11 18:16:47 Age [y:d:h:m:s]: 03:358:08:29:39
Block: 372264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1032229 RingCT/type: yes/0
Extra: 01e0b75f1616b64f8d4d33810e3e9a9a1313a8e7185afd90659aa2bdf9e0213e45021100000001f56b629f000000000000000000

1 output(s) for total of 35.853802746000 dcy

stealth address amount amount idx
00: dc35fab4c2259bf22a6f1ce4100fe7c90ef2108736a46f315541322aa84c2d5e 35.853802746000 754140 of 0

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": 372274, "vin": [ { "gen": { "height": 372264 } } ], "vout": [ { "amount": 35853802746, "target": { "key": "dc35fab4c2259bf22a6f1ce4100fe7c90ef2108736a46f315541322aa84c2d5e" } } ], "extra": [ 1, 224, 183, 95, 22, 22, 182, 79, 141, 77, 51, 129, 14, 62, 154, 154, 19, 19, 168, 231, 24, 90, 253, 144, 101, 154, 162, 189, 249, 224, 33, 62, 69, 2, 17, 0, 0, 0, 1, 245, 107, 98, 159, 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