Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429306abf5b68bba5eb14730bf98afdcce3f321486fe0a117d1ab5220640f006

Tx prefix hash: 0ea0918cf768154341b93d84835ca8716b940fac98a303d6aa8894e4195044a3
Tx public key: 1a556475dc2f0f2e0c7067f9b6bdd03f82b99d886a675b5ef898217cb055a791
Timestamp: 1673114022 Timestamp [UCT]: 2023-01-07 17:53:42 Age [y:d:h:m:s]: 01:329:23:45:56
Block: 669706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496864 RingCT/type: yes/0
Extra: 011a556475dc2f0f2e0c7067f9b6bdd03f82b99d886a675b5ef898217cb055a79102110000000152542ceb000000000000000000

1 output(s) for total of 3.706687483000 dcy

stealth address amount amount idx
00: b3311077c123a7960aa1c9a218f44f234da512eb041c2e93a89cc87a9462fd29 3.706687483000 1111063 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": 669716, "vin": [ { "gen": { "height": 669706 } } ], "vout": [ { "amount": 3706687483, "target": { "key": "b3311077c123a7960aa1c9a218f44f234da512eb041c2e93a89cc87a9462fd29" } } ], "extra": [ 1, 26, 85, 100, 117, 220, 47, 15, 46, 12, 112, 103, 249, 182, 189, 208, 63, 130, 185, 157, 136, 106, 103, 91, 94, 248, 152, 33, 124, 176, 85, 167, 145, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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