Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32effa54c5a7387e3adc15320cfbd6f4ef10eed60e63c8d6c2ce80f648ab29a8

Tx prefix hash: 0b71d587071dea0e2d7e330f2334f7731820147e1de57238f662dd1d0bee31fa
Tx public key: 7cc0e965c54efff8aec30209ff6025da59ffe569075f7f3e5a1a351a5bca0965
Timestamp: 1673648790 Timestamp [UCT]: 2023-01-13 22:26:30 Age [y:d:h:m:s]: 02:118:06:58:58
Block: 674133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606244 RingCT/type: yes/0
Extra: 017cc0e965c54efff8aec30209ff6025da59ffe569075f7f3e5a1a351a5bca0965021100000003044c7254000000000000000000

1 output(s) for total of 3.583583071000 dcy

stealth address amount amount idx
00: 53c1e10b7f321239aecaa11a3939d7ca49b1dd53dd9a38ff35e4493e19acc61a 3.583583071000 1115774 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": 674143, "vin": [ { "gen": { "height": 674133 } } ], "vout": [ { "amount": 3583583071, "target": { "key": "53c1e10b7f321239aecaa11a3939d7ca49b1dd53dd9a38ff35e4493e19acc61a" } } ], "extra": [ 1, 124, 192, 233, 101, 197, 78, 255, 248, 174, 195, 2, 9, 255, 96, 37, 218, 89, 255, 229, 105, 7, 95, 127, 62, 90, 26, 53, 26, 91, 202, 9, 101, 2, 17, 0, 0, 0, 3, 4, 76, 114, 84, 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