Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c25b4a3bd3e84983ee071e07dfb543079f679ae1b60574b0547014e95469ea00

Tx prefix hash: f5ed6a35f35dfd2daee23bcbe5e07b9da405e503e978e56d1dadfbdf9d607f96
Tx public key: 96725d06e63fc76586e9b354639f8e60bf2c80ec105daf5cc3344828ef770f1c
Timestamp: 1577756995 Timestamp [UCT]: 2019-12-31 01:49:55 Age [y:d:h:m:s]: 04:335:04:43:32
Block: 35416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128672 RingCT/type: yes/0
Extra: 0196725d06e63fc76586e9b354639f8e60bf2c80ec105daf5cc3344828ef770f1c02110000000c4ac5aa02000000000000000000

1 output(s) for total of 468.438891354000 dcy

stealth address amount amount idx
00: 3631280c7b51a5bfb89b5688bd0bd171dbb4b95dd137d47d91734e64c36967a0 468.438891354000 59717 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": 35426, "vin": [ { "gen": { "height": 35416 } } ], "vout": [ { "amount": 468438891354, "target": { "key": "3631280c7b51a5bfb89b5688bd0bd171dbb4b95dd137d47d91734e64c36967a0" } } ], "extra": [ 1, 150, 114, 93, 6, 230, 63, 199, 101, 134, 233, 179, 84, 99, 159, 142, 96, 191, 44, 128, 236, 16, 93, 175, 92, 195, 52, 72, 40, 239, 119, 15, 28, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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