Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd65377002d36f117d229ed0f4b38e8faaf8f89d74299bc84b8c0c9e0bcc5df1

Tx prefix hash: 0c7faf2daee7051e44ed708cdf9de5ced5f82737647c8c1708efc8d247121cab
Tx public key: d331f01e15048952279bc233f6569bcab953b24b27100aa926fee24d36cca1d0
Timestamp: 1681695264 Timestamp [UCT]: 2023-04-17 01:34:24 Age [y:d:h:m:s]: 01:218:02:47:14
Block: 740229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417344 RingCT/type: yes/0
Extra: 01d331f01e15048952279bc233f6569bcab953b24b27100aa926fee24d36cca1d002110000000375e3f0e9000000000000000000

1 output(s) for total of 2.164284040000 dcy

stealth address amount amount idx
00: 1c643b99f1e2796af7b754acd9d4a29e9fdd4c576b910f5fe3e507034e0a0b62 2.164284040000 1187114 of 0

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": 740239, "vin": [ { "gen": { "height": 740229 } } ], "vout": [ { "amount": 2164284040, "target": { "key": "1c643b99f1e2796af7b754acd9d4a29e9fdd4c576b910f5fe3e507034e0a0b62" } } ], "extra": [ 1, 211, 49, 240, 30, 21, 4, 137, 82, 39, 155, 194, 51, 246, 86, 155, 202, 185, 83, 178, 75, 39, 16, 10, 169, 38, 254, 226, 77, 54, 204, 161, 208, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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