Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279d0c265e15b9c90ed3e0887d849a7552969d0ad4027dca1f34713caf9f33da

Tx prefix hash: c6b6eea09b20e817a703d863d2816edc769fd684194138359a59777a6f05d2d2
Tx public key: 3fe259bb88e5d5b4a8e96310c1a467bd01df60515cb5e89cc1022a2345396e12
Timestamp: 1732600103 Timestamp [UCT]: 2024-11-26 05:48:23 Age [y:d:h:m:s]: 00:162:18:28:52
Block: 1161924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116159 RingCT/type: yes/0
Extra: 013fe259bb88e5d5b4a8e96310c1a467bd01df60515cb5e89cc1022a2345396e12021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6a6cff4e3d4982ad273d7c17c72e9cb219780c9585df7e6324292bab981b402 0.600000000000 1647579 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": 1161934, "vin": [ { "gen": { "height": 1161924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6a6cff4e3d4982ad273d7c17c72e9cb219780c9585df7e6324292bab981b402" } } ], "extra": [ 1, 63, 226, 89, 187, 136, 229, 213, 180, 168, 233, 99, 16, 193, 164, 103, 189, 1, 223, 96, 81, 92, 181, 232, 156, 193, 2, 42, 35, 69, 57, 110, 18, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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