Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2740f06271df23383b5f12b07752d2d70e4e05c68f98732d6cd83d28d802d45

Tx prefix hash: efa00d507dfa98829f99417ed377a039b168af7a2e106d5ada8878b099938f74
Tx public key: bd01ee62022c5e42683081dc35b2bdc513e2c7ed2b83ee029accb671f8227223
Timestamp: 1646103243 Timestamp [UCT]: 2022-03-01 02:54:03 Age [y:d:h:m:s]: 03:245:10:13:51
Block: 448777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 953168 RingCT/type: yes/0
Extra: 01bd01ee62022c5e42683081dc35b2bdc513e2c7ed2b83ee029accb671f822722302110000000ca8c141c5000000000000000000

1 output(s) for total of 20.000025510000 dcy

stealth address amount amount idx
00: 7382a1d1feb660f3adac3df760436fadfc987b29cf3b346ef9b05efe353df61f 20.000025510000 863228 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": 448787, "vin": [ { "gen": { "height": 448777 } } ], "vout": [ { "amount": 20000025510, "target": { "key": "7382a1d1feb660f3adac3df760436fadfc987b29cf3b346ef9b05efe353df61f" } } ], "extra": [ 1, 189, 1, 238, 98, 2, 44, 94, 66, 104, 48, 129, 220, 53, 178, 189, 197, 19, 226, 199, 237, 43, 131, 238, 2, 154, 204, 182, 113, 248, 34, 114, 35, 2, 17, 0, 0, 0, 12, 168, 193, 65, 197, 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