Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ce61b8f570edf6146f0fdb71211b1f146314b0033348d2bccc59adf55bbc63

Tx prefix hash: 0e6a841f0d8abd8cb8131af52c3b95a1bb485d52d502e7033facfbc1a3dfa964
Tx public key: 29eaed78f6273d0b46ba7f41c320d316f1c66d21682ca85831650f6e5e744c4e
Timestamp: 1579352912 Timestamp [UCT]: 2020-01-18 13:08:32 Age [y:d:h:m:s]: 04:340:11:49:25
Block: 48364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132762 RingCT/type: yes/0
Extra: 0129eaed78f6273d0b46ba7f41c320d316f1c66d21682ca85831650f6e5e744c4e021100000001dcee4b4d000000000000000000

1 output(s) for total of 424.376011267000 dcy

stealth address amount amount idx
00: 67ade7a7178e31d64abc83b7a3f058bd71c75d8ea24e72c060e46d7e85b52b78 424.376011267000 89541 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": 48374, "vin": [ { "gen": { "height": 48364 } } ], "vout": [ { "amount": 424376011267, "target": { "key": "67ade7a7178e31d64abc83b7a3f058bd71c75d8ea24e72c060e46d7e85b52b78" } } ], "extra": [ 1, 41, 234, 237, 120, 246, 39, 61, 11, 70, 186, 127, 65, 195, 32, 211, 22, 241, 198, 109, 33, 104, 44, 168, 88, 49, 101, 15, 110, 94, 116, 76, 78, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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