Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b3074881e6f8809cb4fe8d423c280516d9fa0c17bda33ecbafe75035c9b0a7a

Tx prefix hash: 411a484cee09eb4cfebdef75486f24091f4c5652e17864eb6135481d0b71b8da
Tx public key: 1683f6e81b9f562ab4e818daa72444ee96e8716036a9b625189295fd73f2ee4d
Timestamp: 1575977116 Timestamp [UCT]: 2019-12-10 11:25:16 Age [y:d:h:m:s]: 05:325:20:56:54
Block: 24764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1376330 RingCT/type: yes/0
Extra: 011683f6e81b9f562ab4e818daa72444ee96e8716036a9b625189295fd73f2ee4d02110000000e9159db1e000000000000000000

1 output(s) for total of 508.097967836000 dcy

stealth address amount amount idx
00: a46c65e9b35aefbd6424e5c3e8a93cb55e76fb9d4bdd41584e96f5452c86fa78 508.097967836000 40691 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": 24774, "vin": [ { "gen": { "height": 24764 } } ], "vout": [ { "amount": 508097967836, "target": { "key": "a46c65e9b35aefbd6424e5c3e8a93cb55e76fb9d4bdd41584e96f5452c86fa78" } } ], "extra": [ 1, 22, 131, 246, 232, 27, 159, 86, 42, 180, 232, 24, 218, 167, 36, 68, 238, 150, 232, 113, 96, 54, 169, 182, 37, 24, 146, 149, 253, 115, 242, 238, 77, 2, 17, 0, 0, 0, 14, 145, 89, 219, 30, 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