Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c15c7bf1ea718e954a02879b1ed757117a87c97840cdf20ee74076c9e5e631a

Tx prefix hash: 74e07154c7826ef21513bb1908450fce1bfe5cbb72b75b74b17893f4d0bb0aa7
Tx public key: 6ea4d4fbbba6de2efd38f932ce25e742f59cb88b45993879d64294583f4450a0
Timestamp: 1734192946 Timestamp [UCT]: 2024-12-14 16:15:46 Age [y:d:h:m:s]: 00:117:04:45:03
Block: 1175127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83536 RingCT/type: yes/0
Extra: 016ea4d4fbbba6de2efd38f932ce25e742f59cb88b45993879d64294583f4450a00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 879c61ea393b7883133f99253d2a526236323cfab30ebc7bea049e5cab08a197 0.600000000000 1661364 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": 1175137, "vin": [ { "gen": { "height": 1175127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879c61ea393b7883133f99253d2a526236323cfab30ebc7bea049e5cab08a197" } } ], "extra": [ 1, 110, 164, 212, 251, 187, 166, 222, 46, 253, 56, 249, 50, 206, 37, 231, 66, 245, 156, 184, 139, 69, 153, 56, 121, 214, 66, 148, 88, 63, 68, 80, 160, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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