Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c619ca36d06d949e395c2a86a5da9e9d230909ca4ebff743d4ca85d857f58b15

Tx prefix hash: 548e586b38e54d9713417ab7acbf70e03599d4cc70d9cab18cb4c154cc5a5013
Tx public key: 6c3a7b7fede5907f9c2db640dd28cd323c0667bc90f44f813f2b8c8b53f5b53e
Timestamp: 1700592551 Timestamp [UCT]: 2023-11-21 18:49:11 Age [y:d:h:m:s]: 02:031:07:54:23
Block: 896657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542206 RingCT/type: yes/0
Extra: 016c3a7b7fede5907f9c2db640dd28cd323c0667bc90f44f813f2b8c8b53f5b53e0211000000024b8f5122000000000000000000

1 output(s) for total of 0.656149991000 dcy

stealth address amount amount idx
00: 0f6694e07b4661543c0863a6fec10d2d8f3df8e84691d0f311aa68650a699325 0.656149991000 1352998 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": 896667, "vin": [ { "gen": { "height": 896657 } } ], "vout": [ { "amount": 656149991, "target": { "key": "0f6694e07b4661543c0863a6fec10d2d8f3df8e84691d0f311aa68650a699325" } } ], "extra": [ 1, 108, 58, 123, 127, 237, 229, 144, 127, 156, 45, 182, 64, 221, 40, 205, 50, 60, 6, 103, 188, 144, 244, 79, 129, 63, 43, 140, 139, 83, 245, 181, 62, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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