Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c41dc88945fc95a8676f3f1df3fcb2dbbcda861d3ba2049c9fc6f3a4e88e268

Tx prefix hash: b2c83df4723891bc822f78fccea7cef87e1da5d99b2e3e39ac62cdd1a83571d1
Tx public key: 8fcb0350fe19a99cfef3958d9a91d1384291180770cdcd3c68754f4d94523ab3
Timestamp: 1736752102 Timestamp [UCT]: 2025-01-13 07:08:22 Age [y:d:h:m:s]: 00:149:12:51:32
Block: 1196298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106676 RingCT/type: yes/0
Extra: 018fcb0350fe19a99cfef3958d9a91d1384291180770cdcd3c68754f4d94523ab3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb3d1a40690a5747e0bcd0a0d9d733a422f827e1d1dd81266fea1950ab96d7d 0.600000000000 1682895 of 15

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": 1196308, "vin": [ { "gen": { "height": 1196298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb3d1a40690a5747e0bcd0a0d9d733a422f827e1d1dd81266fea1950ab96d7d" } } ], "extra": [ 1, 143, 203, 3, 80, 254, 25, 169, 156, 254, 243, 149, 141, 154, 145, 209, 56, 66, 145, 24, 7, 112, 205, 205, 60, 104, 117, 79, 77, 148, 82, 58, 179, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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