Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354e92f4868ed9fbcac8f8acc1fdbd4f105a3d4235aeb44756ce55ffec1616cd

Tx prefix hash: af5a3b73593dc75f4206b0f3b899c85dbefd7c676e0fc469abbf701d9bd99514
Tx public key: 5b0f52eacd7ac9aee3e84f14e4d3cbe1efd6bf0008f60341c88174489c984e18
Timestamp: 1718732778 Timestamp [UCT]: 2024-06-18 17:46:18 Age [y:d:h:m:s]: 01:142:07:34:18
Block: 1047046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360277 RingCT/type: yes/0
Extra: 015b0f52eacd7ac9aee3e84f14e4d3cbe1efd6bf0008f60341c88174489c984e1802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c03a99689fb73d132364fea1d95917813d3aef36a39022aadf864cb7c031f53 0.600000000000 1516865 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": 1047056, "vin": [ { "gen": { "height": 1047046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c03a99689fb73d132364fea1d95917813d3aef36a39022aadf864cb7c031f53" } } ], "extra": [ 1, 91, 15, 82, 234, 205, 122, 201, 174, 227, 232, 79, 20, 228, 211, 203, 225, 239, 214, 191, 0, 8, 246, 3, 65, 200, 129, 116, 72, 156, 152, 78, 24, 2, 17, 0, 0, 0, 3, 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