Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4c5f8623a2574a0ca2087530764e5d422436291c1f90b7a726f0b767597eee

Tx prefix hash: f6b45932dd4fee81d3bd312577bff09b8c96e17cd47eeb186a4985386b740e91
Tx public key: 1cddb9f8d123cd05757425f256c8b729f04824bee0a9809fc2587b1a40362c60
Timestamp: 1716493820 Timestamp [UCT]: 2024-05-23 19:50:20 Age [y:d:h:m:s]: 00:244:00:07:57
Block: 1028494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174585 RingCT/type: yes/0
Extra: 011cddb9f8d123cd05757425f256c8b729f04824bee0a9809fc2587b1a40362c600211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f6af9da47f71fd26c9952543e3f596fae8793dcbb355bdae0a2504fc6bfafc 0.600000000000 1496487 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": 1028504, "vin": [ { "gen": { "height": 1028494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f6af9da47f71fd26c9952543e3f596fae8793dcbb355bdae0a2504fc6bfafc" } } ], "extra": [ 1, 28, 221, 185, 248, 209, 35, 205, 5, 117, 116, 37, 242, 86, 200, 183, 41, 240, 72, 36, 190, 224, 169, 128, 159, 194, 88, 123, 26, 64, 54, 44, 96, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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