Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31aa628a4a5287c87e6382691e28bb1c5a5e2dad89f081455152824c1ffce98d

Tx prefix hash: 0983acb4883a251342394b7399ae192facb7dfc29a49175bb209bf022b7a311d
Tx public key: 1e7a450fb9ed6ddf216624fe68af44a5f5f0a12b2074083f628357592c16a3ea
Timestamp: 1721890878 Timestamp [UCT]: 2024-07-25 07:01:18 Age [y:d:h:m:s]: 00:166:04:08:14
Block: 1073223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118899 RingCT/type: yes/0
Extra: 011e7a450fb9ed6ddf216624fe68af44a5f5f0a12b2074083f628357592c16a3ea021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb448f6a55ccc85637e325c0f348394f0fcfee922fce4bbbbccfd022a2e9f6f6 0.600000000000 1545722 of 15

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": 1073233, "vin": [ { "gen": { "height": 1073223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb448f6a55ccc85637e325c0f348394f0fcfee922fce4bbbbccfd022a2e9f6f6" } } ], "extra": [ 1, 30, 122, 69, 15, 185, 237, 109, 223, 33, 102, 36, 254, 104, 175, 68, 165, 245, 240, 161, 43, 32, 116, 8, 63, 98, 131, 87, 89, 44, 22, 163, 234, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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