Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7373dd7b6e5eaaa26581a0659b6337025b0729df8543656549b858b86eb348b8

Tx prefix hash: d2db3beea2ec0452271672ae365e279082e8f5badb290a61525f5ac263a832de
Tx public key: b7842fc6fb53f2783a4e10cc0f838f3f19c934ef90d4302d8dfd712c42413e1a
Timestamp: 1699619027 Timestamp [UCT]: 2023-11-10 12:23:47 Age [y:d:h:m:s]: 01:151:08:09:38
Block: 888592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369342 RingCT/type: yes/0
Extra: 01b7842fc6fb53f2783a4e10cc0f838f3f19c934ef90d4302d8dfd712c42413e1a021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.697791752000 dcy

stealth address amount amount idx
00: 8ff980b5e2b7316f7ccb7b2b2bb3276b656c23fb5a4dbecdf3e596e872888f06 0.697791752000 1344539 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": 888602, "vin": [ { "gen": { "height": 888592 } } ], "vout": [ { "amount": 697791752, "target": { "key": "8ff980b5e2b7316f7ccb7b2b2bb3276b656c23fb5a4dbecdf3e596e872888f06" } } ], "extra": [ 1, 183, 132, 47, 198, 251, 83, 242, 120, 58, 78, 16, 204, 15, 131, 143, 63, 25, 201, 52, 239, 144, 212, 48, 45, 141, 253, 113, 44, 66, 65, 62, 26, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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