Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0f0f2c45d5b2521371531a6f89306706ac53eaf6d0d5b0ac93c9f67b8f6ca67

Tx prefix hash: 3e0676486e7215af10cce248021991e2de9ccee30defd8ce2becafb5832453d5
Tx public key: 5c264539a14a5718c9f72a9d10f2b295ca090bf562f93592836647a88ebf55a2
Timestamp: 1716778602 Timestamp [UCT]: 2024-05-27 02:56:42 Age [y:d:h:m:s]: 00:292:11:58:41
Block: 1030859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209057 RingCT/type: yes/0
Extra: 015c264539a14a5718c9f72a9d10f2b295ca090bf562f93592836647a88ebf55a20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dc7b04f3a84b2447f7d715c17d024101d9d235d2e930edccd07b9af9af5e642 0.600000000000 1499168 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": 1030869, "vin": [ { "gen": { "height": 1030859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dc7b04f3a84b2447f7d715c17d024101d9d235d2e930edccd07b9af9af5e642" } } ], "extra": [ 1, 92, 38, 69, 57, 161, 74, 87, 24, 201, 247, 42, 157, 16, 242, 178, 149, 202, 9, 11, 245, 98, 249, 53, 146, 131, 102, 71, 168, 142, 191, 85, 162, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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