Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c2abe51a44250112667de74a02ad6c8d8c5dba663bab062115a2e5ad055343

Tx prefix hash: e67f7880babb39ab51e29f74045879b959a3abc6437447c6a1691f5e6f930a59
Tx public key: 6af6e4161086ca59df2f73eeee1a5365969b0cf3fe8c7f042c6ac09ca4115662
Timestamp: 1634685699 Timestamp [UCT]: 2021-10-19 23:21:39 Age [y:d:h:m:s]: 03:031:04:11:35
Block: 356484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 800363 RingCT/type: yes/0
Extra: 016af6e4161086ca59df2f73eeee1a5365969b0cf3fe8c7f042c6ac09ca41156620211000000558d0de867000000000000000000

1 output(s) for total of 40.440911773000 dcy

stealth address amount amount idx
00: 0d41989f32dc8c2e5228de6a15599d248bd01ea8c3636ae5a28e0ddd9c4c1059 40.440911773000 727322 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": 356494, "vin": [ { "gen": { "height": 356484 } } ], "vout": [ { "amount": 40440911773, "target": { "key": "0d41989f32dc8c2e5228de6a15599d248bd01ea8c3636ae5a28e0ddd9c4c1059" } } ], "extra": [ 1, 106, 246, 228, 22, 16, 134, 202, 89, 223, 47, 115, 238, 238, 26, 83, 101, 150, 155, 12, 243, 254, 140, 127, 4, 44, 106, 192, 156, 164, 17, 86, 98, 2, 17, 0, 0, 0, 85, 141, 13, 232, 103, 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