Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533f48da200fa9544455a03daafcae89d3c5a2e6204fea4f917fa82cd35974a8

Tx prefix hash: fe596531bdc7cb7d3bf8692e7d02ca5b44ea7995304313d1a7ba95db156199f4
Tx public key: f92f931e07e58043c2510da68c617bb8d28cfaed10c530204d35f5a8680a86bc
Timestamp: 1716213920 Timestamp [UCT]: 2024-05-20 14:05:20 Age [y:d:h:m:s]: 00:332:15:43:06
Block: 1026169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237770 RingCT/type: yes/0
Extra: 01f92f931e07e58043c2510da68c617bb8d28cfaed10c530204d35f5a8680a86bc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee1f6f720068d507b5b8bf4aaf2119b2ae093d4d7b41143344d1993466dc8427 0.600000000000 1493106 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": 1026179, "vin": [ { "gen": { "height": 1026169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee1f6f720068d507b5b8bf4aaf2119b2ae093d4d7b41143344d1993466dc8427" } } ], "extra": [ 1, 249, 47, 147, 30, 7, 229, 128, 67, 194, 81, 13, 166, 140, 97, 123, 184, 210, 140, 250, 237, 16, 197, 48, 32, 77, 53, 245, 168, 104, 10, 134, 188, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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