Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e2b756f427813972ff45cf03d408f54b81ccf44f1a4d382eacea2c0b2c2055

Tx prefix hash: d0cf934798996476dd828a6e2b776b1f4d1fb96752acf9ce0b15b7e6119a5fa7
Tx public key: 7ce22dccd54f8b9fdf0049cc3d8db5f3df63d59118428de5e5642b7c55eb10e6
Timestamp: 1578849644 Timestamp [UCT]: 2020-01-12 17:20:44 Age [y:d:h:m:s]: 05:029:02:23:09
Block: 44114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170892 RingCT/type: yes/0
Extra: 017ce22dccd54f8b9fdf0049cc3d8db5f3df63d59118428de5e5642b7c55eb10e602110000001c4ac5aa02000000000000000000

1 output(s) for total of 438.404286814000 dcy

stealth address amount amount idx
00: b78d0ca565bf33a4361b190bbc3c73a6e19b8227d974030ad5ddbbb676b1e4ce 438.404286814000 80166 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": 44124, "vin": [ { "gen": { "height": 44114 } } ], "vout": [ { "amount": 438404286814, "target": { "key": "b78d0ca565bf33a4361b190bbc3c73a6e19b8227d974030ad5ddbbb676b1e4ce" } } ], "extra": [ 1, 124, 226, 45, 204, 213, 79, 139, 159, 223, 0, 73, 204, 61, 141, 181, 243, 223, 99, 213, 145, 24, 66, 141, 229, 229, 100, 43, 124, 85, 235, 16, 230, 2, 17, 0, 0, 0, 28, 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