Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936f97a7c0b3ddeedb4e2c7dfe08068c70ad654c55fdf7d744e6665e8db1d221

Tx prefix hash: 35fd327f27307cb94f25b4e83bb8209da24c8c2407525c537316ec153fa2e5a9
Tx public key: 2287fda58f1dcd76524bf0c0fc24fc9a6134cb61b2bd8d79bbde08dea87e490e
Timestamp: 1735258788 Timestamp [UCT]: 2024-12-27 00:19:48 Age [y:d:h:m:s]: 00:096:08:24:39
Block: 1183933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68643 RingCT/type: yes/0
Extra: 012287fda58f1dcd76524bf0c0fc24fc9a6134cb61b2bd8d79bbde08dea87e490e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b78450696660e4dbd3cd54ddb5a653517453f5da5392c6bc344e85a331bfd995 0.600000000000 1670382 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": 1183943, "vin": [ { "gen": { "height": 1183933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b78450696660e4dbd3cd54ddb5a653517453f5da5392c6bc344e85a331bfd995" } } ], "extra": [ 1, 34, 135, 253, 165, 143, 29, 205, 118, 82, 75, 240, 192, 252, 36, 252, 154, 97, 52, 203, 97, 178, 189, 141, 121, 187, 222, 8, 222, 168, 126, 73, 14, 2, 17, 0, 0, 0, 4, 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