Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c038c9cdafae483f19f9edff753981e854e748ab36d94f52e075d70aaf16c15a

Tx prefix hash: b0886de6b5b4cbe9b9ea3a3c1b82f473ff21e46a6dd0f37903558c8e1d7b559c
Tx public key: 71761f1c3ce5e7d00f94e914ceae600333be40b5e4e7a72db6c9eeaa92351185
Timestamp: 1702807310 Timestamp [UCT]: 2023-12-17 10:01:50 Age [y:d:h:m:s]: 01:150:14:38:02
Block: 915020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368793 RingCT/type: yes/0
Extra: 0171761f1c3ce5e7d00f94e914ceae600333be40b5e4e7a72db6c9eeaa92351185021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce9a316720e777cb26fdf4aed4c00827e60303d2e12b6075a0b6037e49f78575 0.600000000000 1372388 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": 915030, "vin": [ { "gen": { "height": 915020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce9a316720e777cb26fdf4aed4c00827e60303d2e12b6075a0b6037e49f78575" } } ], "extra": [ 1, 113, 118, 31, 28, 60, 229, 231, 208, 15, 148, 233, 20, 206, 174, 96, 3, 51, 190, 64, 181, 228, 231, 167, 45, 182, 201, 238, 170, 146, 53, 17, 133, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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