Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9932ab0413540e12d71fd07658c54021eae9935b7c8e3232f64ac2df96a20acf

Tx prefix hash: dba693a5f4778e42319b678996c0f91ac88481b4d1205bf080a609056ec67261
Tx public key: c510c3e5f09aacae38cf6a0f0dff3963292b80e3b6e2eabd6b9fe81b6a15f4a0
Timestamp: 1711667161 Timestamp [UCT]: 2024-03-28 23:06:01 Age [y:d:h:m:s]: 01:047:07:37:15
Block: 988487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294802 RingCT/type: yes/0
Extra: 01c510c3e5f09aacae38cf6a0f0dff3963292b80e3b6e2eabd6b9fe81b6a15f4a002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d2bf5bbd2eae363a7ef3c61874ae0ce4dfc41ffde90937771e829bffce8711 0.600000000000 1448766 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": 988497, "vin": [ { "gen": { "height": 988487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d2bf5bbd2eae363a7ef3c61874ae0ce4dfc41ffde90937771e829bffce8711" } } ], "extra": [ 1, 197, 16, 195, 229, 240, 154, 172, 174, 56, 207, 106, 15, 13, 255, 57, 99, 41, 43, 128, 227, 182, 226, 234, 189, 107, 159, 232, 27, 106, 21, 244, 160, 2, 17, 0, 0, 0, 7, 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