Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a06bb2efb48bb3c1ffed33747057ad72d8d8f3bbceae8b92113e69117919b65c

Tx prefix hash: 6d095068d20ede4910d824328c377c431608ed7b165a9884d59a8a18109eb001
Tx public key: 2e769e172a5c69f18d2d2e6f6f26545add53979901c3aa7bd47abb3778cf49ce
Timestamp: 1583077197 Timestamp [UCT]: 2020-03-01 15:39:57 Age [y:d:h:m:s]: 04:320:12:20:48
Block: 74506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123118 RingCT/type: yes/0
Extra: 012e769e172a5c69f18d2d2e6f6f26545add53979901c3aa7bd47abb3778cf49ce0211000000a4c71d3ff9000000000000000000

1 output(s) for total of 347.647400693000 dcy

stealth address amount amount idx
00: c125e0e4bf5ce90325fdcce75038f90cbc8bff61cf15992e8d6fb22f4b19be88 347.647400693000 137877 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": 74516, "vin": [ { "gen": { "height": 74506 } } ], "vout": [ { "amount": 347647400693, "target": { "key": "c125e0e4bf5ce90325fdcce75038f90cbc8bff61cf15992e8d6fb22f4b19be88" } } ], "extra": [ 1, 46, 118, 158, 23, 42, 92, 105, 241, 141, 45, 46, 111, 111, 38, 84, 90, 221, 83, 151, 153, 1, 195, 170, 123, 212, 122, 187, 55, 120, 207, 73, 206, 2, 17, 0, 0, 0, 164, 199, 29, 63, 249, 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