Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65d1f2cf27eb157a9604a41f71c1bc8ce987ebd957d537a3d313defcf261b0a

Tx prefix hash: 702fc2f2c890c3f136c3924df40905bab4ed2844f39efd11072090220725ba67
Tx public key: 4bcfec3829689c6f029a40c5c0ae333e84798d6d04cd3c03a905397c6c8249d2
Timestamp: 1726057495 Timestamp [UCT]: 2024-09-11 12:24:55 Age [y:d:h:m:s]: 00:210:18:21:57
Block: 1107776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150473 RingCT/type: yes/0
Extra: 014bcfec3829689c6f029a40c5c0ae333e84798d6d04cd3c03a905397c6c8249d202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0c6af5a04d5024fcb5ec126e1f585eeb82499df10501e336280b9f642b16a44 0.600000000000 1585433 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": 1107786, "vin": [ { "gen": { "height": 1107776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0c6af5a04d5024fcb5ec126e1f585eeb82499df10501e336280b9f642b16a44" } } ], "extra": [ 1, 75, 207, 236, 56, 41, 104, 156, 111, 2, 154, 64, 197, 192, 174, 51, 62, 132, 121, 141, 109, 4, 205, 60, 3, 169, 5, 57, 124, 108, 130, 73, 210, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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