Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549140ac74a5617d1f5366f6437bfbc103adb7a891fd87a3e7911aeb116d708c

Tx prefix hash: 2724fe74d71b9965ed9c56057af54a0fd564f49cf32d63fb4c6df532e61f0d5d
Tx public key: b37458e59515bde896e7e23aff3a5d7af061eb9aa5d4bd5753f6af19c4f8101a
Timestamp: 1704881898 Timestamp [UCT]: 2024-01-10 10:18:18 Age [y:d:h:m:s]: 01:089:23:16:20
Block: 932208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325404 RingCT/type: yes/0
Extra: 01b37458e59515bde896e7e23aff3a5d7af061eb9aa5d4bd5753f6af19c4f8101a02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca6b7be3cc85c0da54164fb66b38a6baf0b3c6c6e3b75351027a32439ff09aa0 0.600000000000 1390134 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": 932218, "vin": [ { "gen": { "height": 932208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca6b7be3cc85c0da54164fb66b38a6baf0b3c6c6e3b75351027a32439ff09aa0" } } ], "extra": [ 1, 179, 116, 88, 229, 149, 21, 189, 232, 150, 231, 226, 58, 255, 58, 93, 122, 240, 97, 235, 154, 165, 212, 189, 87, 83, 246, 175, 25, 196, 248, 16, 26, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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