Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be8c38b0bb91998d44304e463f9523b20a4009f2b035ab7e962242c484eb03ef

Tx prefix hash: e6d0f8343046aba28179614d77f5693a98d19217ee548cc9d038bb7e5f647720
Tx public key: 9fb1e28a1d30dc2141a6aeccefe5c5aa435b7fbdb0114a392dcd760ab91fc9d3
Timestamp: 1733587240 Timestamp [UCT]: 2024-12-07 16:00:40 Age [y:d:h:m:s]: 00:111:05:42:33
Block: 1170096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79292 RingCT/type: yes/0
Extra: 019fb1e28a1d30dc2141a6aeccefe5c5aa435b7fbdb0114a392dcd760ab91fc9d3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102fa77829eed71e28dcbdc0f003d304c81fb1de08f8db31e9f5fc9013bb3910 0.600000000000 1655825 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": 1170106, "vin": [ { "gen": { "height": 1170096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102fa77829eed71e28dcbdc0f003d304c81fb1de08f8db31e9f5fc9013bb3910" } } ], "extra": [ 1, 159, 177, 226, 138, 29, 48, 220, 33, 65, 166, 174, 204, 239, 229, 197, 170, 67, 91, 127, 189, 176, 17, 74, 57, 45, 205, 118, 10, 185, 31, 201, 211, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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