Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f8d9cebb410d4b5be178b59072cbcf30e071d035c186a656944eb13db9dbbac

Tx prefix hash: 95bc5d0da0a1b3b1be62a86b66c202578a7ed13d277aa2996a714ee7f3a23abc
Tx public key: 8b301ea739a88aea7ef0ce27ba42f74246f58f08ce6b103109d12fa95c62f052
Timestamp: 1730406669 Timestamp [UCT]: 2024-10-31 20:31:09 Age [y:d:h:m:s]: 00:023:17:30:37
Block: 1143753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16982 RingCT/type: yes/0
Extra: 018b301ea739a88aea7ef0ce27ba42f74246f58f08ce6b103109d12fa95c62f052021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b006be00a2c8872e1a375c0c7fee2597e7d1bc0340c7436ac187b078d5af6c 0.600000000000 1627734 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": 1143763, "vin": [ { "gen": { "height": 1143753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b006be00a2c8872e1a375c0c7fee2597e7d1bc0340c7436ac187b078d5af6c" } } ], "extra": [ 1, 139, 48, 30, 167, 57, 168, 138, 234, 126, 240, 206, 39, 186, 66, 247, 66, 70, 245, 143, 8, 206, 107, 16, 49, 9, 209, 47, 169, 92, 98, 240, 82, 2, 17, 0, 0, 0, 2, 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