Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62a60619975182a6ad00ce7961c0a5fd5520db8e25329b5628ef5818582445cd

Tx prefix hash: 6495923deb94d1a15d05f74b6d2d26f728682c37ac972df56206d2c11af0f973
Tx public key: 10f9bdf0d0608bda907d2a54535e1ba77fe9f73e2cd10ba755b8a85ca6d94553
Timestamp: 1706094526 Timestamp [UCT]: 2024-01-24 11:08:46 Age [y:d:h:m:s]: 01:084:08:16:38
Block: 942240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321377 RingCT/type: yes/0
Extra: 0110f9bdf0d0608bda907d2a54535e1ba77fe9f73e2cd10ba755b8a85ca6d945530211000000078cc46cda000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170f30a5d6d0e24db9e5ecf8ca025a305002cb8e9aa7849f7d949cf43249f4be 0.600000000000 1400406 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": 942250, "vin": [ { "gen": { "height": 942240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170f30a5d6d0e24db9e5ecf8ca025a305002cb8e9aa7849f7d949cf43249f4be" } } ], "extra": [ 1, 16, 249, 189, 240, 208, 96, 139, 218, 144, 125, 42, 84, 83, 94, 27, 167, 127, 233, 247, 62, 44, 209, 11, 167, 85, 184, 168, 92, 166, 217, 69, 83, 2, 17, 0, 0, 0, 7, 140, 196, 108, 218, 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