Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a84171d07cb9457731135dbfcd0dfa9f691456a0c3720df784cedf40c9ebfa1

Tx prefix hash: 6cca728acb76440a3fda556d7fb8f56533a68237c4f001f5d1e80b3a0b4189ae
Tx public key: 27e85b427d6dfbf27d3ee32c3160267dcf16565897245c180afe7801aabe602b
Timestamp: 1694780256 Timestamp [UCT]: 2023-09-15 12:17:36 Age [y:d:h:m:s]: 01:161:20:16:34
Block: 848656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376718 RingCT/type: yes/0
Extra: 0127e85b427d6dfbf27d3ee32c3160267dcf16565897245c180afe7801aabe602b021100000007faf35c9c000000000000000000

1 output(s) for total of 0.946347059000 dcy

stealth address amount amount idx
00: 193541e0aa40d4bc116f69f08b7aa74c5f030cd24fca0bf4bd50fa1c712eed09 0.946347059000 1302274 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": 848666, "vin": [ { "gen": { "height": 848656 } } ], "vout": [ { "amount": 946347059, "target": { "key": "193541e0aa40d4bc116f69f08b7aa74c5f030cd24fca0bf4bd50fa1c712eed09" } } ], "extra": [ 1, 39, 232, 91, 66, 125, 109, 251, 242, 125, 62, 227, 44, 49, 96, 38, 125, 207, 22, 86, 88, 151, 36, 92, 24, 10, 254, 120, 1, 170, 190, 96, 43, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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