Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 836d041357fae891071bf14f28e107b2c571bb19b0b8c903444cbe11cae3cbd4

Tx prefix hash: 855e5d1e60c6648995b45472cff2d0e0c0759f076965a776cb255517a53c8da7
Tx public key: 3c4cae37af0330715ff9fd4664c02037aff2e52ac117bf2f29f468923b2da8ef
Timestamp: 1684631136 Timestamp [UCT]: 2023-05-21 01:05:36 Age [y:d:h:m:s]: 01:320:20:46:18
Block: 764582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490530 RingCT/type: yes/0
Extra: 013c4cae37af0330715ff9fd4664c02037aff2e52ac117bf2f29f468923b2da8ef02110000000133af99f4000000000000000000

1 output(s) for total of 1.797308477000 dcy

stealth address amount amount idx
00: 3a02f38d720086424e304bae9e86e82d961b995e443a0e6f0b831a6bbdacd4c9 1.797308477000 1213525 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": 764592, "vin": [ { "gen": { "height": 764582 } } ], "vout": [ { "amount": 1797308477, "target": { "key": "3a02f38d720086424e304bae9e86e82d961b995e443a0e6f0b831a6bbdacd4c9" } } ], "extra": [ 1, 60, 76, 174, 55, 175, 3, 48, 113, 95, 249, 253, 70, 100, 192, 32, 55, 175, 242, 229, 42, 193, 23, 191, 47, 41, 244, 104, 146, 59, 45, 168, 239, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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