Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c90d9b8e290ef3bf21e214bc29c1f41f256d2c4fd55173162c5fde25a0027cf5

Tx prefix hash: a1045e5f5a61ae0399a01dcd4537e9c7428385c7ba5eea0e0a88e0c323eadc48
Tx public key: cd1d4929cf34be996ab1284b884d6496c839bf2cface28fd58b4e12e38afecd7
Timestamp: 1726271618 Timestamp [UCT]: 2024-09-13 23:53:38 Age [y:d:h:m:s]: 01:056:12:21:28
Block: 1109545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298811 RingCT/type: yes/0
Extra: 01cd1d4929cf34be996ab1284b884d6496c839bf2cface28fd58b4e12e38afecd7021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 470f4f03fb3e55ec6298965d400190b30034195a1d3ecb2a1064927e5a252e55 0.600000000000 1587836 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": 1109555, "vin": [ { "gen": { "height": 1109545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "470f4f03fb3e55ec6298965d400190b30034195a1d3ecb2a1064927e5a252e55" } } ], "extra": [ 1, 205, 29, 73, 41, 207, 52, 190, 153, 106, 177, 40, 75, 136, 77, 100, 150, 200, 57, 191, 44, 250, 206, 40, 253, 88, 180, 225, 46, 56, 175, 236, 215, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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