Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985c770579b89c2431b800f09617a8e918d4cf40b4f5db2be84489d49fc94a28

Tx prefix hash: 95689d795d038dce9864ebc675b183caf352466221a1fe4e299016048a60ac03
Tx public key: ebe968c0b2332d8d0eaa65a0330ed142402ca8902aae36b01a6b9710f00f3db1
Timestamp: 1712157291 Timestamp [UCT]: 2024-04-03 15:14:51 Age [y:d:h:m:s]: 01:041:23:19:06
Block: 992513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291007 RingCT/type: yes/0
Extra: 01ebe968c0b2332d8d0eaa65a0330ed142402ca8902aae36b01a6b9710f00f3db102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87850ae77243da8a13acd729d3317167b9c681922c87795c21224aeaef1e25ea 0.600000000000 1452857 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": 992523, "vin": [ { "gen": { "height": 992513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87850ae77243da8a13acd729d3317167b9c681922c87795c21224aeaef1e25ea" } } ], "extra": [ 1, 235, 233, 104, 192, 178, 51, 45, 141, 14, 170, 101, 160, 51, 14, 209, 66, 64, 44, 168, 144, 42, 174, 54, 176, 26, 107, 151, 16, 240, 15, 61, 177, 2, 17, 0, 0, 0, 4, 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