Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0779426c2af7523b6b8e53c3f93412cba0851fd5b2ee6fafdd9b40dfa3d7e5b6

Tx prefix hash: f3c470fe70d0f6a1017e360de25b940c991b8737facd82d3278238d242a7757e
Tx public key: 262773c2fa11e5ed1dc7a3a66897e4d7a16bb31ce26d5b2dec48ac2e112113c8
Timestamp: 1699529179 Timestamp [UCT]: 2023-11-09 11:26:19 Age [y:d:h:m:s]: 01:150:00:33:19
Block: 887854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368394 RingCT/type: yes/0
Extra: 01262773c2fa11e5ed1dc7a3a66897e4d7a16bb31ce26d5b2dec48ac2e112113c802110000000433af99f4000000000000000000

1 output(s) for total of 0.701731761000 dcy

stealth address amount amount idx
00: dba521be24b98f0dc198ab663691ea0e333e7f9232bcfd56c86bfc556c6d82d9 0.701731761000 1343761 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": 887864, "vin": [ { "gen": { "height": 887854 } } ], "vout": [ { "amount": 701731761, "target": { "key": "dba521be24b98f0dc198ab663691ea0e333e7f9232bcfd56c86bfc556c6d82d9" } } ], "extra": [ 1, 38, 39, 115, 194, 250, 17, 229, 237, 29, 199, 163, 166, 104, 151, 228, 215, 161, 107, 179, 28, 226, 109, 91, 45, 236, 72, 172, 46, 17, 33, 19, 200, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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