Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d001777bb0ba15b909b283fa2e1fb3df9e65a3428384d63ce787e14d1b2ff19c

Tx prefix hash: acff795251d453dc5919cbaf7d3211572e797028417517acc357e5bd3100161f
Tx public key: 69b0c6fbb472da40c7b1f2fd5e5e15957853184af24b5db051108735ad5f3ff1
Timestamp: 1578682845 Timestamp [UCT]: 2020-01-10 19:00:45 Age [y:d:h:m:s]: 05:064:11:56:24
Block: 42918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196034 RingCT/type: yes/0
Extra: 0169b0c6fbb472da40c7b1f2fd5e5e15957853184af24b5db051108735ad5f3ff102110000003ed81c26c0000000000000000000

1 output(s) for total of 442.380212853000 dcy

stealth address amount amount idx
00: 657076c13b9cbf30cf2bf00efbb2da1d71fe65cdd2af9265f49ef4c432a9ada1 442.380212853000 77458 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": 42928, "vin": [ { "gen": { "height": 42918 } } ], "vout": [ { "amount": 442380212853, "target": { "key": "657076c13b9cbf30cf2bf00efbb2da1d71fe65cdd2af9265f49ef4c432a9ada1" } } ], "extra": [ 1, 105, 176, 198, 251, 180, 114, 218, 64, 199, 177, 242, 253, 94, 94, 21, 149, 120, 83, 24, 74, 242, 75, 93, 176, 81, 16, 135, 53, 173, 95, 63, 241, 2, 17, 0, 0, 0, 62, 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