Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271b1bf2272c6dda244dceff1070c526cd40ce5cde4f106c062f68a72ce0d831

Tx prefix hash: 38910d6d197fbe82d3b6a45e49207c675b10e00efc6e54cef996826afd64fcb0
Tx public key: ed82e4414b8e9f0ed54f80275b28ece14bc608e3828010175a22fcc307bf4aef
Timestamp: 1709910945 Timestamp [UCT]: 2024-03-08 15:15:45 Age [y:d:h:m:s]: 01:073:02:14:32
Block: 973912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313267 RingCT/type: yes/0
Extra: 01ed82e4414b8e9f0ed54f80275b28ece14bc608e3828010175a22fcc307bf4aef02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e37aef563c87c6d54dd9c98fd61a7e268e5e4044a63a6eec87c53d7c7760b0f 0.600000000000 1433855 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": 973922, "vin": [ { "gen": { "height": 973912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e37aef563c87c6d54dd9c98fd61a7e268e5e4044a63a6eec87c53d7c7760b0f" } } ], "extra": [ 1, 237, 130, 228, 65, 75, 142, 159, 14, 213, 79, 128, 39, 91, 40, 236, 225, 75, 198, 8, 227, 130, 128, 16, 23, 90, 34, 252, 195, 7, 191, 74, 239, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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