Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 436cf904b1789aa100004d60617cdd10e3d5b1b596f7d5ac2425a59476238fb4

Tx prefix hash: fc28c020b1f801cfedb8d52618a6afeaaee983354b94ffb613ebb4b801889823
Tx public key: f24f2e731ee5410c2c7f836c078eaeeddef9a08a74f867d14a0e3ef16c62d3e6
Timestamp: 1701155059 Timestamp [UCT]: 2023-11-28 07:04:19 Age [y:d:h:m:s]: 01:186:16:10:32
Block: 901316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394625 RingCT/type: yes/0
Extra: 01f24f2e731ee5410c2c7f836c078eaeeddef9a08a74f867d14a0e3ef16c62d3e60211000000014b8f5122000000000000000000

1 output(s) for total of 0.633236470000 dcy

stealth address amount amount idx
00: 6d2f5e21e1f44ba05565d2774f31b64dcb6d7c4dec7b48be306eb2a1e0cdbe79 0.633236470000 1357869 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": 901326, "vin": [ { "gen": { "height": 901316 } } ], "vout": [ { "amount": 633236470, "target": { "key": "6d2f5e21e1f44ba05565d2774f31b64dcb6d7c4dec7b48be306eb2a1e0cdbe79" } } ], "extra": [ 1, 242, 79, 46, 115, 30, 229, 65, 12, 44, 127, 131, 108, 7, 142, 174, 237, 222, 249, 160, 138, 116, 248, 103, 209, 74, 14, 62, 241, 108, 98, 211, 230, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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