Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72039c94fb8bc6445f04c1d1b23c86007e2f42d9590f523780d6f2d2225b6263

Tx prefix hash: 375a1d79fc8c3eeb05b5210f6f0bc784b68cf128be409745917a2550ab551783
Tx public key: 4f7b99c2e803c8af04629df07953eb27483f2d3664e65f3d94f26ee82ff4cdb4
Timestamp: 1705157767 Timestamp [UCT]: 2024-01-13 14:56:07 Age [y:d:h:m:s]: 01:310:09:45:45
Block: 934493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480684 RingCT/type: yes/0
Extra: 014f7b99c2e803c8af04629df07953eb27483f2d3664e65f3d94f26ee82ff4cdb40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a120eecc7fe140e9c8ce6784daa55927bd2f87893aba43f8f67abd5a483756 0.600000000000 1392505 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": 934503, "vin": [ { "gen": { "height": 934493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a120eecc7fe140e9c8ce6784daa55927bd2f87893aba43f8f67abd5a483756" } } ], "extra": [ 1, 79, 123, 153, 194, 232, 3, 200, 175, 4, 98, 157, 240, 121, 83, 235, 39, 72, 63, 45, 54, 100, 230, 95, 61, 148, 242, 110, 232, 47, 244, 205, 180, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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