Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a563de4b4fb1a592c19da3a2e4036229c53eaa578eeb17d0024acbce855d53ca

Tx prefix hash: bf7590ffd2e581f5f8dba2c4b8918e99536a2d78e2a8a8877aa9f0c3edb8af77
Tx public key: 8fe1f34170045523a70bb590316ddfc37929f809ce041a5cc1ec24487e132ae9
Timestamp: 1579140463 Timestamp [UCT]: 2020-01-16 02:07:43 Age [y:d:h:m:s]: 04:295:10:32:27
Block: 46441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100645 RingCT/type: yes/0
Extra: 018fe1f34170045523a70bb590316ddfc37929f809ce041a5cc1ec24487e132ae902110000000e8a2ee0d9000000000000000000

1 output(s) for total of 430.648091226000 dcy

stealth address amount amount idx
00: 680a54b1baef3f7d60b68616da2dcce63626b271a91829ac23da8b47952640a1 430.648091226000 85435 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": 46451, "vin": [ { "gen": { "height": 46441 } } ], "vout": [ { "amount": 430648091226, "target": { "key": "680a54b1baef3f7d60b68616da2dcce63626b271a91829ac23da8b47952640a1" } } ], "extra": [ 1, 143, 225, 243, 65, 112, 4, 85, 35, 167, 11, 181, 144, 49, 109, 223, 195, 121, 41, 248, 9, 206, 4, 26, 92, 193, 236, 36, 72, 126, 19, 42, 233, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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