Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c4e378536f2936150e86ecb946de7de62ebda5d39cc2fc139eb6df6d8199a48

Tx prefix hash: 68edaebc0c269e7744db63d40fbcc4781ea7cd6591259083d60c509b6eb64da9
Tx public key: 014dbe3bb3309bff4b5a9247837b08d9fc7b792820f53b930a96e32d43bcbfe1
Timestamp: 1718856380 Timestamp [UCT]: 2024-06-20 04:06:20 Age [y:d:h:m:s]: 01:217:19:21:09
Block: 1048079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414129 RingCT/type: yes/0
Extra: 01014dbe3bb3309bff4b5a9247837b08d9fc7b792820f53b930a96e32d43bcbfe102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc75ffebe60be4cdacaf5c1dfa07ae5e6d5eeb11a4340f8501a6a5a294f87111 0.600000000000 1518070 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": 1048089, "vin": [ { "gen": { "height": 1048079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc75ffebe60be4cdacaf5c1dfa07ae5e6d5eeb11a4340f8501a6a5a294f87111" } } ], "extra": [ 1, 1, 77, 190, 59, 179, 48, 155, 255, 75, 90, 146, 71, 131, 123, 8, 217, 252, 123, 121, 40, 32, 245, 59, 147, 10, 150, 227, 45, 67, 188, 191, 225, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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