Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d58c4866697419607e398d472dea9a8df1359b276eb386f6a8c0676dad84eb

Tx prefix hash: ea7e5f54aa620e4407e32c03f6ad84b36a49e6fbb9a90ba2e0233292f788f596
Tx public key: d60155e91defe26f404df118beeb28334f16fc5e7dafe82a38a607a73f37a8e1
Timestamp: 1681237931 Timestamp [UCT]: 2023-04-11 18:32:11 Age [y:d:h:m:s]: 01:236:06:05:02
Block: 736438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430333 RingCT/type: yes/0
Extra: 01d60155e91defe26f404df118beeb28334f16fc5e7dafe82a38a607a73f37a8e1021100000001b3164c24000000000000000000

1 output(s) for total of 2.227795996000 dcy

stealth address amount amount idx
00: fd79f996995a276f5b47e6ed61a917358f94c8e0d340dfcf13b7efc7def3d6b7 2.227795996000 1182871 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": 736448, "vin": [ { "gen": { "height": 736438 } } ], "vout": [ { "amount": 2227795996, "target": { "key": "fd79f996995a276f5b47e6ed61a917358f94c8e0d340dfcf13b7efc7def3d6b7" } } ], "extra": [ 1, 214, 1, 85, 233, 29, 239, 226, 111, 64, 77, 241, 24, 190, 235, 40, 51, 79, 22, 252, 94, 125, 175, 232, 42, 56, 166, 7, 167, 63, 55, 168, 225, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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