Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829f9c3446fc7d3ea95c1458a334a2dcdad567a2643687f52a8b85127c51b112

Tx prefix hash: d9993335588f2b1bb4b910017068d5ab0d9c7da41103da65063c1b12a24b8d13
Tx public key: 3bc320c90c695dbbbc75450e0cf8d6fca6a23f2af98eb57efd7f2aa6b1a585d8
Timestamp: 1713870118 Timestamp [UCT]: 2024-04-23 11:01:58 Age [y:d:h:m:s]: 00:205:19:23:36
Block: 1006739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147312 RingCT/type: yes/0
Extra: 013bc320c90c695dbbbc75450e0cf8d6fca6a23f2af98eb57efd7f2aa6b1a585d80211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d8bfa49897dc9d1a66834a15763d40a62ccbf10ffafa28b034ea75c675f742a 0.600000000000 1467861 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": 1006749, "vin": [ { "gen": { "height": 1006739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d8bfa49897dc9d1a66834a15763d40a62ccbf10ffafa28b034ea75c675f742a" } } ], "extra": [ 1, 59, 195, 32, 201, 12, 105, 93, 187, 188, 117, 69, 14, 12, 248, 214, 252, 166, 162, 63, 42, 249, 142, 181, 126, 253, 127, 42, 166, 177, 165, 133, 216, 2, 17, 0, 0, 0, 7, 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