Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d4d14f783fee2582513c984e61f46b72a3341cabd3cda7a9649b80575698ea1

Tx prefix hash: 5d52f5d82b846f2a37a96975e1696543016b7eb10f9de7cd17d1ad74a984190e
Tx public key: c8bce9afbea6d14ac2ec77079ced2cb7fc6ffb78df566b1fc90f60bd6b36633e
Timestamp: 1702809646 Timestamp [UCT]: 2023-12-17 10:40:46 Age [y:d:h:m:s]: 01:158:16:07:01
Block: 915049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374565 RingCT/type: yes/0
Extra: 01c8bce9afbea6d14ac2ec77079ced2cb7fc6ffb78df566b1fc90f60bd6b36633e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db5a0cafd2f98e1db4028a6094f37910cde8654ab42b41f0077474f12c842f37 0.600000000000 1372425 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": 915059, "vin": [ { "gen": { "height": 915049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db5a0cafd2f98e1db4028a6094f37910cde8654ab42b41f0077474f12c842f37" } } ], "extra": [ 1, 200, 188, 233, 175, 190, 166, 209, 74, 194, 236, 119, 7, 156, 237, 44, 183, 252, 111, 251, 120, 223, 86, 107, 31, 201, 15, 96, 189, 107, 54, 99, 62, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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