Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36d8e97cbbfb310ea2027403bbcb71fb9c1ee662f7af1eeb12bbd6d0a422498

Tx prefix hash: e19dbd3ef86dabeb493c91454b62cf0d15874a5e9206be24c1a693eccf9c90ed
Tx public key: 4666f4f808cd47d4e1f9979e014145198cf11f2a84d67223ba895388df28b2bc
Timestamp: 1673974577 Timestamp [UCT]: 2023-01-17 16:56:17 Age [y:d:h:m:s]: 02:115:10:00:35
Block: 676842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604173 RingCT/type: yes/0
Extra: 014666f4f808cd47d4e1f9979e014145198cf11f2a84d67223ba895388df28b2bc0211000000018b7b6602000000000000000000

1 output(s) for total of 3.510277341000 dcy

stealth address amount amount idx
00: 9e06befdb452acd6c15a863e891a4d83221500a3fd53f186e5c2e309b4970c43 3.510277341000 1118597 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": 676852, "vin": [ { "gen": { "height": 676842 } } ], "vout": [ { "amount": 3510277341, "target": { "key": "9e06befdb452acd6c15a863e891a4d83221500a3fd53f186e5c2e309b4970c43" } } ], "extra": [ 1, 70, 102, 244, 248, 8, 205, 71, 212, 225, 249, 151, 158, 1, 65, 69, 25, 140, 241, 31, 42, 132, 214, 114, 35, 186, 137, 83, 136, 223, 40, 178, 188, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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