Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c19378af8bb37aace7aa416c1641c8bb12120bdd1a26571019d53d0dcec2b4

Tx prefix hash: d2eb3bf3708e1f073d521e6a7b435f6d4c5f948a7b6d812a9ff9d53202a796db
Tx public key: 7ce87363f433a8ad0118504c6fb7b27c4e5c8b7313ea80e520f8d8500faef322
Timestamp: 1674622827 Timestamp [UCT]: 2023-01-25 05:00:27 Age [y:d:h:m:s]: 02:083:00:54:29
Block: 682232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581001 RingCT/type: yes/0
Extra: 017ce87363f433a8ad0118504c6fb7b27c4e5c8b7313ea80e520f8d8500faef322021100000003272bcc39000000000000000000

1 output(s) for total of 3.368853422000 dcy

stealth address amount amount idx
00: f812214970926bc9488c5f51f0f2ed3a6ae5a75f319c32f5b6da814f79a1921e 3.368853422000 1124347 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": 682242, "vin": [ { "gen": { "height": 682232 } } ], "vout": [ { "amount": 3368853422, "target": { "key": "f812214970926bc9488c5f51f0f2ed3a6ae5a75f319c32f5b6da814f79a1921e" } } ], "extra": [ 1, 124, 232, 115, 99, 244, 51, 168, 173, 1, 24, 80, 76, 111, 183, 178, 124, 78, 92, 139, 115, 19, 234, 128, 229, 32, 248, 216, 80, 15, 174, 243, 34, 2, 17, 0, 0, 0, 3, 39, 43, 204, 57, 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