Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: badefab8efb8fdb1afc243cd3cb772cb472e9f5c9829d5772b67f351cf298ce7

Tx prefix hash: 262cb99880b3d2cc34169f44d472d03d70c905eee807ff9042733f60e640e1a3
Tx public key: c3639c2a4ccd7a50753197996bc6076b9576f1c87af510ee8bb6f2d67511780c
Timestamp: 1699840595 Timestamp [UCT]: 2023-11-13 01:56:35 Age [y:d:h:m:s]: 01:068:00:40:13
Block: 890435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309981 RingCT/type: yes/0
Extra: 01c3639c2a4ccd7a50753197996bc6076b9576f1c87af510ee8bb6f2d67511780c02110000000233af99f4000000000000000000

1 output(s) for total of 0.688048742000 dcy

stealth address amount amount idx
00: b8b31730902730831501c55f7eb59a81ff2e9bc81f8dc6c9d79cec1234954e4a 0.688048742000 1346458 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": 890445, "vin": [ { "gen": { "height": 890435 } } ], "vout": [ { "amount": 688048742, "target": { "key": "b8b31730902730831501c55f7eb59a81ff2e9bc81f8dc6c9d79cec1234954e4a" } } ], "extra": [ 1, 195, 99, 156, 42, 76, 205, 122, 80, 117, 49, 151, 153, 107, 198, 7, 107, 149, 118, 241, 200, 122, 245, 16, 238, 139, 182, 242, 214, 117, 17, 120, 12, 2, 17, 0, 0, 0, 2, 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