Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d38839f287a914edee1fc351f25a0f341fb19fe509a582ea110d640afb9983

Tx prefix hash: 9b65c90277b217e4e4e3f7ebfcd489c10015cba685590d2e4984ae1fb5e62ea9
Tx public key: 8a8fbc6630c6820bad0cd5bcb676db4b898aba823d6bb08c65a449d523df624c
Timestamp: 1578750556 Timestamp [UCT]: 2020-01-11 13:49:16 Age [y:d:h:m:s]: 05:023:05:02:07
Block: 43268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166695 RingCT/type: yes/0
Extra: 018a8fbc6630c6820bad0cd5bcb676db4b898aba823d6bb08c65a449d523df624c0211000000024ac5aa02000000000000000000

1 output(s) for total of 441.200501526000 dcy

stealth address amount amount idx
00: f5e2a6ca6d3ac5872b148f15f66ac5ce7ee47781e7faba2d6d90e5fc7a2b42cb 441.200501526000 78281 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": 43278, "vin": [ { "gen": { "height": 43268 } } ], "vout": [ { "amount": 441200501526, "target": { "key": "f5e2a6ca6d3ac5872b148f15f66ac5ce7ee47781e7faba2d6d90e5fc7a2b42cb" } } ], "extra": [ 1, 138, 143, 188, 102, 48, 198, 130, 11, 173, 12, 213, 188, 182, 118, 219, 75, 137, 138, 186, 130, 61, 107, 176, 140, 101, 164, 73, 213, 35, 223, 98, 76, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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