Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d9cb6595ab4e08bbec931b2d51784206675259b2a98be293089537e9a56cafb

Tx prefix hash: 21986ba44515a58851d3a69893cc6db904dff1fabad3bf2fc08e4f6975fd043e
Tx public key: 91a5059f63aee0b08e54a66f8ae01b2cab9a50a5d89fceb8dd7f4ad0e9dfa5a1
Timestamp: 1673104114 Timestamp [UCT]: 2023-01-07 15:08:34 Age [y:d:h:m:s]: 02:053:03:24:01
Block: 669622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559636 RingCT/type: yes/0
Extra: 0191a5059f63aee0b08e54a66f8ae01b2cab9a50a5d89fceb8dd7f4ad0e9dfa5a102110000000252542ceb000000000000000000

1 output(s) for total of 3.709063755000 dcy

stealth address amount amount idx
00: ec63cf80f67db25712e2bc745ec7f6efa0ef66ac3b9f3cbf6e52a1d3c38c4182 3.709063755000 1110967 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": 669632, "vin": [ { "gen": { "height": 669622 } } ], "vout": [ { "amount": 3709063755, "target": { "key": "ec63cf80f67db25712e2bc745ec7f6efa0ef66ac3b9f3cbf6e52a1d3c38c4182" } } ], "extra": [ 1, 145, 165, 5, 159, 99, 174, 224, 176, 142, 84, 166, 111, 138, 224, 27, 44, 171, 154, 80, 165, 216, 159, 206, 184, 221, 127, 74, 208, 233, 223, 165, 161, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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