Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbd2f957e8586b986c309f270f11f5ce3ed12d76c6f22a28e7ae27d8154fce4c

Tx prefix hash: e247616e2ab0dcfa5ef41b7341fb54e2628228202a018a0f308fa2f132171df3
Tx public key: b2e15d3a5ac320d0631ae60624d6b3f567537f87f8d3634e14c4938ed2246231
Timestamp: 1727483497 Timestamp [UCT]: 2024-09-28 00:31:37 Age [y:d:h:m:s]: 00:168:22:52:10
Block: 1119597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120578 RingCT/type: yes/0
Extra: 01b2e15d3a5ac320d0631ae60624d6b3f567537f87f8d3634e14c4938ed2246231021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2bd9129aff16bd59910801a83e186b39b98cab3e04e04c785288e1a76f591a0 0.600000000000 1601210 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": 1119607, "vin": [ { "gen": { "height": 1119597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2bd9129aff16bd59910801a83e186b39b98cab3e04e04c785288e1a76f591a0" } } ], "extra": [ 1, 178, 225, 93, 58, 90, 195, 32, 208, 99, 26, 230, 6, 36, 214, 179, 245, 103, 83, 127, 135, 248, 211, 99, 78, 20, 196, 147, 142, 210, 36, 98, 49, 2, 17, 0, 0, 0, 2, 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