Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e7e1c7643e4c628d154fb0e29a4fbb509766c2bcdd0278f53e095151ce5567f

Tx prefix hash: 99a34c9fa93da212261be76292e76d9d7d90742201841ff11eafcd050296fee3
Tx public key: bd4c503deabc1c17fa632a993d67ae60c891799772b3ff330c31a726bb4f141b
Timestamp: 1723167281 Timestamp [UCT]: 2024-08-09 01:34:41 Age [y:d:h:m:s]: 00:107:20:15:10
Block: 1083804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77157 RingCT/type: yes/0
Extra: 01bd4c503deabc1c17fa632a993d67ae60c891799772b3ff330c31a726bb4f141b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 038973e89ee7be55dc4eb5a7c029ca01d4bde0ed7ec2a98abd7af5de0d9ca1b9 0.600000000000 1557859 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": 1083814, "vin": [ { "gen": { "height": 1083804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "038973e89ee7be55dc4eb5a7c029ca01d4bde0ed7ec2a98abd7af5de0d9ca1b9" } } ], "extra": [ 1, 189, 76, 80, 61, 234, 188, 28, 23, 250, 99, 42, 153, 61, 103, 174, 96, 200, 145, 121, 151, 114, 179, 255, 51, 12, 49, 167, 38, 187, 79, 20, 27, 2, 17, 0, 0, 0, 5, 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