Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f3deb1bd117bdb7729852b0c0156e41c5912e8afb95b5e5a711863a5871b443

Tx prefix hash: 2e809abec4ffd2fc7491c51ed219fddb8437a1fa44ac576c23279cfa924263b1
Tx public key: 7a6b2410f57673307dde036f0f909050929f08d9d0501d4730752f62bd2b41a1
Timestamp: 1711651382 Timestamp [UCT]: 2024-03-28 18:43:02 Age [y:d:h:m:s]: 01:004:02:35:36
Block: 988361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263866 RingCT/type: yes/0
Extra: 017a6b2410f57673307dde036f0f909050929f08d9d0501d4730752f62bd2b41a102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d266c96c5ca18f50852e920d876579f1970649f70d48ffe09df926d7e0ff34f 0.600000000000 1448638 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": 988371, "vin": [ { "gen": { "height": 988361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d266c96c5ca18f50852e920d876579f1970649f70d48ffe09df926d7e0ff34f" } } ], "extra": [ 1, 122, 107, 36, 16, 245, 118, 115, 48, 125, 222, 3, 111, 15, 144, 144, 80, 146, 159, 8, 217, 208, 80, 29, 71, 48, 117, 47, 98, 189, 43, 65, 161, 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