Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fa8db51c91c9a4367c5df8aaab4ddfe8a58f36f54623e95860993345dc0258d

Tx prefix hash: bed56129b8781884c5271a7d8460750ad51f5fae2674ea156676dea7b4129fcd
Tx public key: 8966f0dc92ffaf2a7d47db9dfbf8ca770a2a008d32a7ad13bf17be4979362884
Timestamp: 1634798245 Timestamp [UCT]: 2021-10-21 06:37:25 Age [y:d:h:m:s]: 03:143:06:20:15
Block: 357278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 880424 RingCT/type: yes/0
Extra: 018966f0dc92ffaf2a7d47db9dfbf8ca770a2a008d32a7ad13bf17be497936288402110000004f7e786c8c000000000000000000

1 output(s) for total of 40.196670863000 dcy

stealth address amount amount idx
00: bfc286825ed917ca503e284100b54c3015815a5a312f837d616e0c3cd328f8f3 40.196670863000 728580 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": 357288, "vin": [ { "gen": { "height": 357278 } } ], "vout": [ { "amount": 40196670863, "target": { "key": "bfc286825ed917ca503e284100b54c3015815a5a312f837d616e0c3cd328f8f3" } } ], "extra": [ 1, 137, 102, 240, 220, 146, 255, 175, 42, 125, 71, 219, 157, 251, 248, 202, 119, 10, 42, 0, 141, 50, 167, 173, 19, 191, 23, 190, 73, 121, 54, 40, 132, 2, 17, 0, 0, 0, 79, 126, 120, 108, 140, 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