Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7f44069d8c3f44eb5870afc2b35958e1da92c774ad5ce919ed7e720cd43149f

Tx prefix hash: 098e81374af5f59ad685c5db5d36c1e872d9010160d2bc3bb1825d50d382740f
Tx public key: 1db482fcd518ec733a6a7521be805fde3df6dbf2cfb9159973930e82620a3000
Timestamp: 1607588190 Timestamp [UCT]: 2020-12-10 08:16:30 Age [y:d:h:m:s]: 03:294:17:57:53
Block: 159375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 961705 RingCT/type: yes/0
Extra: 011db482fcd518ec733a6a7521be805fde3df6dbf2cfb9159973930e82620a300002110000000357f0ba47000000000000000000

1 output(s) for total of 181.950454887000 dcy

stealth address amount amount idx
00: 561c4d342f5e6685f139583a80dc5e5f43b67e9e03637d7db2a3d91118206f2e 181.950454887000 278588 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": 159385, "vin": [ { "gen": { "height": 159375 } } ], "vout": [ { "amount": 181950454887, "target": { "key": "561c4d342f5e6685f139583a80dc5e5f43b67e9e03637d7db2a3d91118206f2e" } } ], "extra": [ 1, 29, 180, 130, 252, 213, 24, 236, 115, 58, 106, 117, 33, 190, 128, 95, 222, 61, 246, 219, 242, 207, 185, 21, 153, 115, 147, 14, 130, 98, 10, 48, 0, 2, 17, 0, 0, 0, 3, 87, 240, 186, 71, 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