Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1662e9411042dfacc48535d7c4ff7375a1828ccda65014a7dc182083885118b

Tx prefix hash: bcd53068e8d7aa4c78c5f96a9b455d587554e786410cfa8546bfc6ac916bf2dc
Tx public key: bb8f797643f41a4d92252c67bbe29c1c2ddc987f4940cd99df4b3bab062d31ad
Timestamp: 1717539322 Timestamp [UCT]: 2024-06-04 22:15:22 Age [y:d:h:m:s]: 00:300:00:14:34
Block: 1037167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214392 RingCT/type: yes/0
Extra: 01bb8f797643f41a4d92252c67bbe29c1c2ddc987f4940cd99df4b3bab062d31ad0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769fee6a0cb40ed17ff46deae98f6f517cae1ee73a4b70edc9dddcfd8eba26c4 0.600000000000 1505698 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": 1037177, "vin": [ { "gen": { "height": 1037167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769fee6a0cb40ed17ff46deae98f6f517cae1ee73a4b70edc9dddcfd8eba26c4" } } ], "extra": [ 1, 187, 143, 121, 118, 67, 244, 26, 77, 146, 37, 44, 103, 187, 226, 156, 28, 45, 220, 152, 127, 73, 64, 205, 153, 223, 75, 59, 171, 6, 45, 49, 173, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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