Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb5b6ddc68fe2ea817a8e6e5d6f545f4c96fef1d94c7ca38a8b78e0bde3c7f0

Tx prefix hash: 45df98d04ebd8460610d4f925c01abe1afc031a0d5a94bcbaee37a77d1850a19
Tx public key: edb9e5809f32705c1c19290e793006c43cb0a21a0d6916cf2bd2f8eab2057f91
Timestamp: 1634744289 Timestamp [UCT]: 2021-10-20 15:38:09 Age [y:d:h:m:s]: 03:076:07:51:16
Block: 356878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 832757 RingCT/type: yes/0
Extra: 01edb9e5809f32705c1c19290e793006c43cb0a21a0d6916cf2bd2f8eab2057f910211000000093fc41461000000000000000000

1 output(s) for total of 40.319529207000 dcy

stealth address amount amount idx
00: fa00752bd78f04eb402c7aaedddec37ce9b61109ded86c5eeb1bffff3c6bad81 40.319529207000 727950 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": 356888, "vin": [ { "gen": { "height": 356878 } } ], "vout": [ { "amount": 40319529207, "target": { "key": "fa00752bd78f04eb402c7aaedddec37ce9b61109ded86c5eeb1bffff3c6bad81" } } ], "extra": [ 1, 237, 185, 229, 128, 159, 50, 112, 92, 28, 25, 41, 14, 121, 48, 6, 196, 60, 176, 162, 26, 13, 105, 22, 207, 43, 210, 248, 234, 178, 5, 127, 145, 2, 17, 0, 0, 0, 9, 63, 196, 20, 97, 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