Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc49360e634b2b73437d7e82144f014da3fcd9fffd8b46a485d633c040e55ee2

Tx prefix hash: b9f8b1f94f9f1e09575ba4196b002ba2d055848d6dfbf8de67093392a0e25f55
Tx public key: 438d6e3f3e1d30436e2528cb318ea098ee65b4ba9276843bc3e4f341a0584a00
Timestamp: 1695966779 Timestamp [UCT]: 2023-09-29 05:52:59 Age [y:d:h:m:s]: 01:048:04:38:55
Block: 858508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295678 RingCT/type: yes/0
Extra: 01438d6e3f3e1d30436e2528cb318ea098ee65b4ba9276843bc3e4f341a0584a00021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.877822395000 dcy

stealth address amount amount idx
00: cba28af716b488ac5515ae2d6c2ac81b58c1e453ffefb0206a9543677e59f407 0.877822395000 1312688 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": 858518, "vin": [ { "gen": { "height": 858508 } } ], "vout": [ { "amount": 877822395, "target": { "key": "cba28af716b488ac5515ae2d6c2ac81b58c1e453ffefb0206a9543677e59f407" } } ], "extra": [ 1, 67, 141, 110, 63, 62, 29, 48, 67, 110, 37, 40, 203, 49, 142, 160, 152, 238, 101, 180, 186, 146, 118, 132, 59, 195, 228, 243, 65, 160, 88, 74, 0, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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