Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f126ecb0eb361b4e5abcdf7aeee5b50678ec637cfaef83bc6071650afab880

Tx prefix hash: 278635a29b060305be84e38b10c23105d087e6d0b2b361cc9512292d1f19300a
Tx public key: a6796d83f89d415eb38006d50cc29dcbe3139a1bb2f242e44aa3ddebb6f5bfc5
Timestamp: 1631169210 Timestamp [UCT]: 2021-09-09 06:33:30 Age [y:d:h:m:s]: 03:112:09:24:23
Block: 330297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855523 RingCT/type: yes/0
Extra: 01a6796d83f89d415eb38006d50cc29dcbe3139a1bb2f242e44aa3ddebb6f5bfc502110000000b8d0de867000000000000000000

1 output(s) for total of 49.384353453000 dcy

stealth address amount amount idx
00: df4f829270923ea42c66f2a7935e27c0b86456bfd04793fc51fac99b1cfc9a0a 49.384353453000 682974 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": 330307, "vin": [ { "gen": { "height": 330297 } } ], "vout": [ { "amount": 49384353453, "target": { "key": "df4f829270923ea42c66f2a7935e27c0b86456bfd04793fc51fac99b1cfc9a0a" } } ], "extra": [ 1, 166, 121, 109, 131, 248, 157, 65, 94, 179, 128, 6, 213, 12, 194, 157, 203, 227, 19, 154, 27, 178, 242, 66, 228, 74, 163, 221, 235, 182, 245, 191, 197, 2, 17, 0, 0, 0, 11, 141, 13, 232, 103, 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