Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 277b21b5ecc75e3878439ea57fdd1e644a682a692b52753e90d0e2edef9c25fe

Tx prefix hash: 366c3ad49e41969309785e61dc6316e743db5157dc0689e012a1a6ffec079cbd
Tx public key: 3f496429aff4ee8f90cbd15fc17776248dd8490fe58da8c3e184f29bd7f3cb19
Timestamp: 1674353014 Timestamp [UCT]: 2023-01-22 02:03:34 Age [y:d:h:m:s]: 02:291:08:57:19
Block: 679988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727609 RingCT/type: yes/0
Extra: 013f496429aff4ee8f90cbd15fc17776248dd8490fe58da8c3e184f29bd7f3cb19021100000006272bcc39000000000000000000

1 output(s) for total of 3.427026180000 dcy

stealth address amount amount idx
00: fbaa7b7b123b0fc8b05157ae47321955fe827df9ab4c2f22fd957b148a97d969 3.427026180000 1122011 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": 679998, "vin": [ { "gen": { "height": 679988 } } ], "vout": [ { "amount": 3427026180, "target": { "key": "fbaa7b7b123b0fc8b05157ae47321955fe827df9ab4c2f22fd957b148a97d969" } } ], "extra": [ 1, 63, 73, 100, 41, 175, 244, 238, 143, 144, 203, 209, 95, 193, 119, 118, 36, 141, 216, 73, 15, 229, 141, 168, 195, 225, 132, 242, 155, 215, 243, 203, 25, 2, 17, 0, 0, 0, 6, 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