Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57fa5299515117fb608a5b6565d474a00931f9b1751349c970c6a6692a08035

Tx prefix hash: 29f5f8decb31274d62cbafa8abce33d420563d82dd2ad48745290895e272b244
Tx public key: 5accfee73b20a4ca235e184f64231e6ad1a1f381736aa9d85d4a342d234ff990
Timestamp: 1576450454 Timestamp [UCT]: 2019-12-15 22:54:14 Age [y:d:h:m:s]: 05:023:03:23:26
Block: 27876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163275 RingCT/type: yes/0
Extra: 015accfee73b20a4ca235e184f64231e6ad1a1f381736aa9d85d4a342d234ff990021100000072d81c26c0000000000000000000

1 output(s) for total of 496.176402007000 dcy

stealth address amount amount idx
00: 2fd769f346d134a09e6f6e33cfa2b9a169ff7d40b6650fa0110a85c018ae69dd 496.176402007000 46042 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": 27886, "vin": [ { "gen": { "height": 27876 } } ], "vout": [ { "amount": 496176402007, "target": { "key": "2fd769f346d134a09e6f6e33cfa2b9a169ff7d40b6650fa0110a85c018ae69dd" } } ], "extra": [ 1, 90, 204, 254, 231, 59, 32, 164, 202, 35, 94, 24, 79, 100, 35, 30, 106, 209, 161, 243, 129, 115, 106, 169, 216, 93, 74, 52, 45, 35, 79, 249, 144, 2, 17, 0, 0, 0, 114, 216, 28, 38, 192, 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